From: Guest section DW <dwguest@win.tue.nl>
To: Kenneth Johansson <ken@canit.se>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXT2 Filesystem permissions (bug)?
Date: Wed, 27 Jun 2001 02:02:37 +0200 [thread overview]
Message-ID: <20010627020237.A24622@win.tue.nl> (raw)
In-Reply-To: <m28zigi7m4.fsf@boreas.yi.org.> <Pine.LNX.4.30.0106251729450.18996-100000@coredump.sh0n.net> <9h8b8q$s95$1@cesium.transmeta.com> <3B390B48.D444B7C5@canit.se>
In-Reply-To: <3B390B48.D444B7C5@canit.se>; from Kenneth Johansson on Wed, Jun 27, 2001 at 12:23:04AM +0200
"H. Peter Anvin" wrote:
:: It's neither a bug nor undocumented.
Kenneth Johansson wrote:
: Interesting but I wonder how much this helps someone that not already know
: what it is. Should not the ls manual also contain something that explains
In fact the best info is on the stat page:
...
The set GID bit (S_ISGID) has several special uses: For a
directory it indicates that BSD semantics is to be used
for that directory: files created there inherit their
group ID from the directory, not from the effective gid of
the creating process, and directories created there will
also get the S_ISGID bit set. For a file that does not
have the group execution bit (S_IXGRP) set, it indicates
mandatory file/record locking.
The `sticky' bit (S_ISVTX) on a directory means that a
file in that directory can be renamed or deleted only by
the owner of the file, by the owner of the directory, and
by root.
...
next prev parent reply other threads:[~2001-06-27 0:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 15:26 VM tuning through fault trace gathering [with actual code] John Fremlin
2001-06-25 17:57 ` Rik van Riel
2001-06-25 21:15 ` John Fremlin
2001-06-25 21:33 ` EXT2 Filesystem permissions (bug)? Shawn Starr
2001-06-25 21:42 ` H. Peter Anvin
2001-06-25 22:20 ` Shawn Starr
2001-06-26 22:23 ` Kenneth Johansson
2001-06-26 22:40 ` Hua Zhong
2001-06-26 23:04 ` Albert D. Cahalan
2001-06-27 0:02 ` Guest section DW [this message]
2001-06-27 9:37 ` Luigi Genoni
2001-06-25 21:47 ` Andreas Dilger
2001-06-25 22:10 ` Luigi Genoni
2001-06-26 0:53 ` VM tuning through fault trace gathering [with actual code] Marcelo Tosatti
2001-06-26 12:54 ` John Fremlin
2001-06-26 13:52 ` Marcelo Tosatti
2001-06-26 15:38 ` John Fremlin
2001-06-27 10:09 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010627020237.A24622@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=hpa@zytor.com \
--cc=ken@canit.se \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®