| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
enumerated list and fix a typo. From Aaron Hawley.
|
|
(Conditional Executability, Numeric Modes):
These days the sticky bit is more often uses as the restricted
deletion flag, so modernize the discussion about this.
(Mode Structure): Linux/GNU -> GNU/Linux.
(Symbolic Modes): Don't imply that "+ur" or "u" is valid.
(Setting Permissions): Don't imply that "+t" is invalid.
Use "rwx" rather than the less-common "rxw" in an example.
(Copying Permissions): Say that ugo is a replacement for
a string of the other letters. Add spaces around examples.
Use "set-user-ID" rather than "set user ID" to avoid ambiguity.
Use "+t" rather than "o+t", since POSIX doesn't specify the latter.
Mention which combinations are portable and which are GNU.
(Numeric Modes): Don't imply they aren't portable; they are
nowadays.
|
|
than "filesystem", as POSIX prefers it with a space.
|
|
permissions and that mounting a filesystem as read-only may
override actual file permissions. Use @command instead
of @code for program names.
|
|
/restricted deletion flag/
|
|
|
|
which is the term that POSIX d5 uses for this notion.
|
|
`a' in the USERS part of a symbolic mode does not cause the special
permissions to be affected... It doesn't reflect what the code does
and isn't required by POSIX. Reported by aldomel@ix.netcom.com via
Mike Stone.
|
|
|
|
|
|
|
|
|
|
|
