file system police.

branches: 1.30.14;
Sort SEE ALSO.

Add userlevel manifestations of posix_fallocate and fdiscard, in
unistd.h and libc, and add a man page.

Allow wiggle room in the man page for implementations of fallocate
that either (a) don't fully unwind on failure, leaving new blocks
allocated without changing the file size, or (b) create only in-memory
transient reservations that disappear when crashing or rebooting.

Also, add crossreference to fdiscard from ftruncate(2), and remove the
old BUGS entry from there that called for a generalized version that
allows discarding ranges of a file: that's what fdiscard is.

Sort errors.

Follow OpenGroup online documents for truncate[1] and ftruncate[2].
Fail with EINVAL for length argument negative values.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/truncate.html
[2] http://pubs.opengroup.org/onlinepubs/9699919799/functions/ftruncate.html

branches: 1.26.8; 1.26.12; 1.26.22;
Consistently use `.Brq Dv XXX' across syscalls man pages, for NAME_MAX
and PATH_MAX.

Describe how to portable extend a file. From joerg. Bump date.

Move previously added sentence to STANDARDS section, as suggested by yamt.

Mention that extending files with truncate is a POSIX extension.
Requested by joerg.

Bump date.

branches: 1.22.10; 1.22.16;
More detailed errors [forgot to commit this a while ago]

\- is a minus, not -.

Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22280, verified by myself.

Use
.In header.h
instead of
.Fd #include \*[Lt]header.h\*[Gt]
Much easier to read and write, and supported by groff for ages.
Okayed by ross.

Merge the nathanw_sa branch.

New sentence, new line. From Robert Elz.

add a portablility note. from openbsd.

Generate <>& symbolically. I'm avoiding .../dist/... directories for now.

Sort sections, sort SEE ALSO, punctuation and miscellanous fixes.

Boring whitespace fixes.

branches: 1.12.4;
Merge duplicate mentions of EPERM, EACCESS, ... into one entry
(where applicable).

update to match current common implementation on NetBSD - [f]truncate()
normally lengtens the file if it's shorter than specified length
also change wording slighly, to match wording in SUS

XXX someone should check how much of SUS truncate(2) specification is true
XXX on NetBSD and update this manpage accordingly

branches: 1.10.2;
Add a LIBRARY section to system call manual pages. While it's clear that the
libraries contain stubs only (with minor exceptions a la pipe(2)), the purpose
of this section is to provide linkage information.

branches: 1.9.6;
Last of the .Os cleanups. .Os is defined in the tmac.doc-common file,
so we shouldn't override it with versions in the manpages. Wheee!

first pass at fixing up capitalization of function names and
arguments; ensure that each is correct with respect to the
implementation, rather than being correct as per english.

merge with lite, keeping most local changes. clean up Ids

Remove description of EINVAL, "The pathname contains a character with the
high-order bit set", as this error is obsolete.

Eventually we may want to add code to some of the "optional" filesystems
(msdosfs, etc.) that checks for illegal characters. At that time it would
be appropriate to reintroduce this error with appropriate text. Perhaps
"The pathname contains a character that is not valid for filesystem type".

Use symbolic names {NAME_MAX} & {PATH_MAX} instead of 255 and 1023 in
description of ENAMETOOLONG error.

Use "Er" for argument to -width in the lists in the ERROR sections --- so
the formatting is consistant.

Clean up manpages:
Use .Fn rather than .Nm macro in HISTORY and STANDARDS sections.
Use .At and .St macros instead of spelling out "Version 6 UNIX",
"IEEE 1003.1-1988 (POSIX)", etc.

Add RCS indentifiers.

branches: 1.1.1;
Initial revision