src-test2/bin, branch release/9.0.0

MFC 225908, 225912, 225927:

2011-10-10T11:11:05Z

225908: - Reorder default ps(1) output according to reality. 225912: - there's no reason the semantics of the -x flag are being explained in the -a flag description - be more precise regarding the relation between the -a flag and the security.bsd.see_other_uids sysctl - describe the format of the -t flag's argument - 'con' no longer is a possible entry in the 'TT' column - explain that the 'TT' column refers to pseudo-terminals via mere numbers - add a hint in the 'tt' keyword description that a keyword 'tty' exists, which will give the full terminal pathname 225859: - Correct a typo that was introduced in 225912 Approved by: re (kib)

Fix memory leaks in error cases.

2011-08-27T15:28:57Z

PR: 159011 Submitted by: Henning Petersen Approved by: re (kib) MFC after: 1 week

Rename ki_ocomm to ki_tdname and OCOMMLEN to TDNAMLEN.

2011-07-18T20:06:15Z

Provide backward compatibility defines under BURN_BRIDGES. Suggested by: jhb Reviewed by: emaste Sponsored by: Sandvine Incorporated Approved by: re (kib)

sh(1): Extend documentation about subshells.

2011-07-10T15:02:25Z

Because sh executes commands in subshell environments without forking in more and more cases (particularly from 8.0 on), it makes sense to describe subshell environments more precisely using ideas from POSIX, together with some FreeBSD-specific items. In particular, the hash and times builtins may not behave as if their state is copied for a subshell environment while leaving the parent shell environment unchanged.

Fix style, since this file has just been touched in a major way.

2011-07-09T12:20:15Z

No actual code changes.

Some refactoring for easier maintenance of the code. This is a follow-up

2011-07-09T12:14:57Z

to re-establishment of 64bit arithmetic, but is committed separately, to not obscure that conversion. This commit does not change the observed behaviour of expr in any way. Style will be fixed in a follow-up commit.

Make /bin/expr support 64bit numeric range and range checks by default,

2011-07-09T12:05:53Z

again. This brings back the behaviour of expr in FreeBSD-4, which had been reverted due to an assumed incompatbility with POSIX.1 for FreeBSD-5. This issue has been discussed in the freebsd-standards list, and the consensus was, that POSIX.1 is in fact not violated by this extension, since it affects only cases of POSIX undefined behaviour (overflow of signed long). Other operating systems did upgrade their versions of expr to support 64bit range, after it had been initially brought to FreeBSD. They have used it for a decade without problems, meanwhile. The -e option is retained, but it will only select less strict checking of numeric parameters (leading white-space, leading "+" are allowed and skipped, an empty string is considered to represent 0 in numeric context.) The call of check_utility_compat() as a means of establishing backwards compatibility with FreeBSD-4 is considered obsolete, but preserved in this commit. It is expected to be removed in a later revision of this file. Reviewed by: bde, das, jilles MFC after: 2 month (those parts that do not violate POLA)

Bump date after the previous commit.

2011-07-01T10:57:10Z

Update and sort the list of the available keywords.

2011-07-01T10:54:47Z

sh: Include instead of non-standard .

2011-06-26T20:12:05Z