| Age | Commit message (Collapse) | Author |
|---|
|
Run "make update-copyright".
|
|
Run "make update-copyright".
|
|
Run "make update-copyright".
|
|
Use this command:
git ls-files | grep -v COPYING \
| xargs env UPDATE_COPYRIGHT_USE_INTERVALS=1 \
build-aux/update-copyright
|
|
|
|
* doc/coreutils.texi: Likewise.
* doc/perm.texi: Likewise.
* old/fileutils/NEWS: Likewise.
* old/sh-utils/NEWS: Likewise.
* old/textutils/NEWS: Likewise.
|
|
Reported by Georg Neis as Debian bug 400778.
|
|
|
|
a+s versus +s, and likewise for g+s.
(Numeric Modes): Bring back example of 0055 == 55. 4755 no
longer clears setgid bit on directories.
(Directory Setuid and Setgid): Numeric modes now affect setuid
and setgid on directories only if they set these bits. This
is so that leading 0 has no effect on numeric modes.
|
|
GNU extension, and that other systems behave differently here.
|
|
about distinguishing file mode bits from permissions bits,
and about execute versus search permission. The FreeBSD command
is chflags, not chrflags.
|
|
restricts only unprivileged users.
|
|
setuid and setgid bits on directories.
(Changing Special Mode Bits): Mention that a implies both u and g
for s. Cross reference to new node.
(Numeric Modes): Don't claim that 0055 is the same as 55; this isn't
true any more. Mention new node.
4755 is now like u=rwxs,go=rx,g-s, not like u=rwxs,go=rx.
(Directory Setuid and Setgid): New node.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
