From: arnold@skeeve.com
To: jpl.jpl@gmail.com, doug@cs.dartmouth.edu
Cc: tuhs@tuhs.org
Subject: [TUHS] Additional groups and additional directory permissions
Date: Fri, 02 Aug 2019 02:35:30 -0600 [thread overview]
Message-ID: <201908020835.x728ZUal026532@freefriends.org> (raw)
In-Reply-To: <CAC0cEp8oZ6kYXZGrwSVKM64MdkKCEMnkwu_62k9z+bne9x-Gaw@mail.gmail.com>
[Subject line changed]
Hi.
Doug McIlroy:
> Yet clean as the idea of groups was, it has been used only sporadically
> (in my experience).
I suspect this was true mainly at Research, where the whole place was
not large. Other people, as pointed out, found groups to be very useful.
"John P. Linderman" <jpl.jpl@gmail.com> wrote:
> This changed when you
> could be in multiple groups at the same time (a BSD invention?),
Yes, at 4.2 BSD. The so-called group set.
> and your
> primary group automatically changed to the group owning your current
> working directory (iff you belonged to that group).
No. Your process simply carried around a bunch of groups with it, and if
the group of the directory matched the primary group or a member of the
group set, you got group permission.
Arthur Krewat <krewat@kilonet.net>:
> There's also the setgid bit on directories, that when files are created,
> they will be in the group that the parent directory has on it.
IIRC this was a Sun invention. It was in SunOS 4.x, and may even have
been in SunOS 3.x.
> Also, I don't think it's been mentioned, but there's the setuid bit on
> directories - otherwise known as the sticky bit. When set, even if you
> have rights to "write" the directory (meaning, delete files), you can't
> delete those owned by other users. Useful for /tmp
Also a SunOS invention, IIRC.
> I have no idea what the timeline is for either of these features :)
Timeline is late 80s, SunOS 4.0, I believe. (Larry? :-)
These ideas later propogated into SVR4 / Solaris, Linux and most (if not all)
the other proprietary Unixes.
HTH,
Arnold
next prev parent reply other threads:[~2019-08-02 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 12:35 [TUHS] Who's behind the UNIX filesystem permission Doug McIlroy
2019-08-01 16:22 ` John P. Linderman
2019-08-01 16:35 ` Arthur Krewat
2019-08-02 8:35 ` arnold [this message]
2019-08-02 11:18 ` [TUHS] Additional groups and additional directory permissions Tony Finch
2019-08-04 6:40 ` arnold
2019-08-02 12:45 ` Arthur Krewat
2019-08-02 13:06 ` Clem Cole
2019-08-02 13:28 ` Clem Cole
2019-08-02 19:00 ` Thomas Paulsen
2019-08-01 17:01 ` [TUHS] Who's behind the UNIX filesystem permission Nemo Nusquam
2019-08-01 18:26 ` Arthur Krewat
2019-08-01 20:14 ` Lyndon Nerenberg
2019-08-01 21:23 ` Dave Horsfall
2019-08-02 19:44 [TUHS] Additional groups and additional directory permissions Norman Wilson
2019-08-10 4:02 Kirk McKusick
2019-08-10 6:02 ` Thomas Paulsen
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=201908020835.x728ZUal026532@freefriends.org \
--to=arnold@skeeve.com \
--cc=doug@cs.dartmouth.edu \
--cc=jpl.jpl@gmail.com \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).