| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
bottom of the manpages and order them consistently.
GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.
Found by: mdocml lint run
Reviewed by: ru
|
|
|
|
| |
Reviewed by: ru
|
|
|
|
|
|
| |
in the last modified date.
Noticed by: brueffer [1]
|
|
|
|
| |
Noticed by: ceri
|
|
|
|
|
| |
Prodded by: brueffer
MFC After: 3 days
|
|
|
|
|
|
|
|
|
| |
is seems to be a problem for SUID applications, which we like to
prevent as much as possible.
PR: docs/39530
Submitted by: Soren Spies <sspies at apple dot com>
MFC After: 3 days
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Stop calling system calls "function calls".
Use "The .Fn system call" a-la "The .Nm utility".
When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.
|
|
|
|
|
|
|
|
| |
the correct location--this section consists solely of security
considerations information.
Sponsored by: DARPA, NAI Labs
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
|
| |
- Mention ``eaccess'' in the NAME section.
- Use intro(2) terminology.
- Markup fixes.
Reviewed by: rwatson
|
| |
|
|
|
|
|
|
| |
so man eaccess will return the access(2) man page.
Obtained from: TrustedBSD Project
|
| |
|
|
|
|
|
|
|
|
| |
permissions.
o Add a reference to intro(2) where it is properly documented.
Reviewed by: bde
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
More libraries manpages updates following.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|
|
|
| |
say is means that a pathname had the high-order bit
set, since this is no longer an error.
|
|
|
|
|
|
| |
use ``is expected to conform to'' phrase, not ``conforms to''
Pointed out by: Bruce->NIST-PCTS
|
|
|
|
| |
Obtained from: ftp://netlib.att.com/netlib/att/cs/v7man/man2
|
|
|