Commit Graph

18 Commits

Author SHA1 Message Date
thorpej 3fdac2b8c5 Merge the nathanw_sa branch. 2003-01-18 10:52:16 +00:00
ross dc5571b22e Generate <>& symbolically. I'm avoiding .../dist/... directories for now. 2002-02-08 01:21:55 +00:00
wiz dfcfff97f3 Boring whitespace fixes. 2001-09-16 01:38:59 +00:00
kleink 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
jdolecek 7d96f3efd3 xref symlink(7) 1999-09-26 21:00:25 +00:00
garbled 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
enami 07caf92eec - Don't use captial letter for function name or function args even if
it is at the beginning of a sentence.
- In SYNOPSIS, rename function argument ``file'' to ``path'', since it is
  refered as ``path'' in DESCRIPTION.
- Use ``Fa path'' instead of ``Xr File'', since probably use of Xr is a typo,
  and now function argument is called ``path''.
1997-10-11 03:27:59 +00:00
enami f67a987e2d Acutally, lchmod, lchown and lutimes may set errno to ELOOP. 1997-10-06 08:22:58 +00:00
enami e61b385cbb Add C library interface for new system call lchmod, lchown and lutimes. 1997-10-06 01:12:06 +00:00
mycroft ad2105650e Document futimes(). 1996-04-23 10:34:16 +00:00
cgd d9393d75fb fix pr 1214 slightly differently. i _didn't_ use the .Fa macro to
mark "file," because in context it didn't seem as if the argument was
being literally named.  rather it seemed that the argument's purpose
being described.  (the difference being: "... modification times of the
file named by file" would be a case where the the argument was named,
and thus be used with .Fa.)
1995-07-12 07:18:31 +00:00
cgd 4eab61bd40 merge with lite, keeping most local changes. clean up Ids 1995-02-27 12:31:34 +00:00
jtc 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
jtc 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
jtc 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
jtc eb3ed86c00 Clean up manpage; cross-reference utime(3). 1993-08-14 00:00:56 +00:00
mycroft dfb9caab49 Add RCS indentifiers. 1993-08-01 07:32:48 +00:00
cgd 61f282557f initial import of 386bsd-0.1 sources 1993-03-21 09:45:37 +00:00