src-test2/include, branch release/4.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-03-20T08:47:53Z

'RELENG_4_0_0_RELEASE'. This commit was manufactured to restore the state of the 4.0-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

This commit was manufactured by cvs2svn to create branch 'RELENG_4'.

2000-03-13T04:59:44Z

Do not conditionalize function prototype definition for functions we

2000-02-20T07:40:25Z

implement. Noticed by: Thimble Smith Approved by: jkh

There is a problem in that one cannot use ctype.h at the same time as parts

2000-02-08T07:43:26Z

of the C++ stdlib. Our ctype.h uses symbols of the form _ to denote the various character classes. Our ctype.h also extends the usual ctype.h offering by adding the "_T" (special) class. Problem is parts of the STL also use the symbol "_T" as its parameterized type. These two uses are incompatible. Thus change the form of the symbols used in ctype to something that fixes the current problem and is less likely to cause conflicts in the future. Requested by: Tomoaki NISHIYAMA Ok'ed by: JKH

Change IPv6 address scope delimeter from '@' to '%' as recent KAME change.

2000-02-08T05:12:45Z

'@' conflicts with existing notations such as user@host, so '%' is better. Approved by: jkh Obtained from: KAME project

Revert part of the last commit, remove {g|s}etflags from the libc

2000-02-05T18:42:36Z

interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh

sync iruserok() extension API with other BSDs

2000-02-01T15:55:56Z

Some of rcmd related function is need to be updated to support IPv6. Some of them are already updated as standard document. But there is also several de-facto functions and they are not listed in standard documents. They are, iruserok() (used by rlogind, rshd) ruserok() (used by kerberos, etc) KAME package updated those functions in original way. iruserok_af() ruserok_af() But recently there was discussion on IETF IPng mailing list about how to sync those API, and it is decided, -Those function is not standard and not documented. -But let BSDs sync their API as de-facto. And after some discussion, it is announced that -add update to iruserok() as iruserok_sa() -no ruserok() API change(it is only updated internaly) So I sync those API before 4.0 is released. The changes are, -prototype changes -ruserok() internal update (use iruserok_sa() inside) -removal of ruserok_af() -change iruserok_af() as static functioin, and also prefix the name with __. -add iruserok_sa() (Just call __iruserok_af() inside) -adding flag AI_ALL to getipnodebyaddr() called from __icheckhost(). This is necessary to support IPv4 communication via AF_INET6 socket could be correctly authenticated via iruserok_sa() -irusreok_af() call is replaced to iruserok_sa() call in rlogind, and rshd. Approved by: jkh

Add a #define for RTLD_LOCAL as required by the Single Unix

2000-01-29T01:53:35Z

Specification.

Historically file flags (schg, uschg, etc) have been converted from

2000-01-27T21:17:01Z

string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. The manual page could probably be improved upon ;)

Sigh. Really fix it this time. It seems the first time through the

2000-01-26T17:38:51Z

run it would modify the source tree, causing it to fail the second time around. Sigh.