73fc291634
Merge duplicate mentions of EPERM, EACCESS, ... into one entry
...
(where applicable).
2000-06-17 19:33:34 +00:00
a6f7a7855f
implement lchflags(2), which does the chflags(2) dance without following
...
symlinks, and thus can operate on symlinks. remove a bogus comment in
chflags(1) that claims symlinks do not have file flags.
XXX: todo -- make chflags(1) use lchflags(2) when given the right options.
2000-04-17 14:31:21 +00:00
15be242b3a
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.
1999-12-02 21:42:35 +00:00
acef34de33
Add note that only the super-user may set or reset any flags on block
...
and character devices. [Commit by cjs.]
1999-07-31 03:30:44 +00:00
38c96853cf
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!
1999-03-22 19:44:33 +00:00
ce83c69e00
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.
1998-08-29 08:32:32 +00:00
af4ebfa68d
.Bx'ize/.Nx'ize
1998-02-03 21:12:45 +00:00
a5c24028fa
merge lite-2
1998-02-02 05:20:24 +00:00
e98ae4a7d1
document new reasons why {,f}chflags() can return EPERM; fixes
...
PR kern/3491. also, fix typo found by Paul Boven.
1997-04-23 06:00:51 +00:00
9c59822c67
add missing opaque and archived bits; from Paul Boven in PR kern/3491.
...
also fixed some formatting nits.
1997-04-22 06:10:26 +00:00
35ccea10a2
fix broken xref, add entries for EOPNOTSUPP, and indicate that this
...
syscall arrived in 4.4BSD.
1997-03-05 06:53:40 +00:00
4eab61bd40
merge with lite, keeping most local changes. clean up Ids
1995-02-27 12:31:34 +00:00
38065bce20
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".
1994-04-22 00:13:22 +00:00
a3376999f0
Use symbolic names {NAME_MAX} & {PATH_MAX} instead of 255 and 1023 in
...
description of ENAMETOOLONG error.
1994-04-19 00:10:45 +00:00
6e9ac1805f
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.
1993-11-25 00:38:17 +00:00
b1bd4afedc
Add RCS indentifiers.
1993-08-01 07:42:49 +00:00
61f282557f
initial import of 386bsd-0.1 sources
1993-03-21 09:45:37 +00:00
hubertf