#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
140420 |
|
18-Jan-2005 |
ru |
Sort sections.
|
#
140368 |
|
17-Jan-2005 |
ru |
Added the EXIT STATUS section where appropriate.
|
#
119893 |
|
08-Sep-2003 |
ru |
mdoc(7): Use the new feature of the .In macro.
|
#
107788 |
|
12-Dec-2002 |
ru |
Uniformly refer to a file system as "file system".
Approved by: re
|
#
107263 |
|
26-Nov-2002 |
ru |
mdoc(7) police: markup nits, "The .Nm utility".
Approved by: re
|
#
103591 |
|
19-Sep-2002 |
wollman |
Completely revamp the way getconf(1) works, for better adherence to the intent of the Standard.
- Make getconf able to distinguish between configuration variables which are entirely unknown and those which are merely not defined in the compilation environment. The latter now get a more appropriate "undefined\n" result rather than a diagnostic. This may not be exactly right, but it's closer to the intent of the Standard than the previous behavior.
- Support ``programming environments'' by validating that the environment requested with the `-v' flag is the one-and-only execution environment. (If more environments are supported for some platforms in the future, multiple getconf(1) executables will be required, but a simple edit in progenv.gperf will enable automatic support for it.) Document POSIX standard programming environments.
- Add all of the 1003.1-2001 configuration variables. FreeBSD does not support all of these (including some that are mandatory); getconf will later be fixed to break the world should a required variable not be defined.
As a result of all these changes, gperf is no longer adequate. Keep the overall format and names of the files for now, to preserve revision history. Use an awk script to process the .gperf files into C source, which does a few things that gperf, as a more general tool, cannot do. The keyword recognition function is no longer a perfect hash function.
This may obviate the need for gperf in the source tree.
- Add a small compile-time regression test to break the build if any of the .gperf files declare conflicting token sets. (gperf itself would have done this for the simple case of duplicate tokens in the same input file.)
|
#
81687 |
|
15-Aug-2001 |
ru |
mdoc(7) police: utilize the new .Ex macro.
|
#
79755 |
|
15-Jul-2001 |
dd |
Remove whitespace at EOL.
|
#
79366 |
|
06-Jul-2001 |
ru |
mdoc(7) police: sort SEE ALSO xrefs (sort -b -f +2 -3 +1 -2).
|
#
72808 |
|
21-Feb-2001 |
wollman |
Reword the description a little bit more for parallel construction.
|
#
72807 |
|
21-Feb-2001 |
wollman |
Destroy the evidence of my misunderstanding of the specification. Also fix up the phrasing in the man page a bit.
|
#
68963 |
|
20-Nov-2000 |
ru |
mdoc(7) police: use the new features of the Nm macro.
|
#
68854 |
|
17-Nov-2000 |
ru |
mdoc(7) police: use certified section headers wherever possible.
|
#
59632 |
|
26-Apr-2000 |
wollman |
Hello, getconf. This is a slight reinvention of the wheel^H^H^H^H^HPOSIX.2 and X/Open utility, and rather more complicated than necessary.
|