From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] Plan9 permissions
Date: Mon, 15 Sep 1997 17:15:13 +0200 [thread overview]
Message-ID: <19970915151513.wCAn03L-dbh_Z5u4crRiWMLddzrsJ6HZuJXVIVKc2Ew@z> (raw)
>
> i don't know. that implies that the log process is not
> running as you, i.e. is running as none or another user, like "upas".
> if another user, then make that user the owner of the file.
> if "none", think strongly about the append-only flag.
> the editors warn about that, and it encourages others not
> to edit the file either.
>
Russ,
you're missing a point here. On the one hand, quite correctly, the
owner has one "permission" bit no-one else can alter, namely ownership.
On the other, making group and other inclusive does not gain you
anything, it is better to make them exclusive, as Unix does, so that
you can stop the owner from accessing something while allowing
arbitrary users, than to have no means whatsoever to achieve this
objective.
There's nothing compulsory about it, nobody has to use the permissions
in this fashion, but removing the facility by opting for the
intuitively obvious approach, decreases the flexibility of the tool.
>From the BSD man pages:
[EACCES] Permission bits of the file mode do not permit the request-
ed access, or search permission is denied on a component of
the path prefix. The owner of a file has permission
checked with respect to the ``owner'' read, write, and exe-
cute mode bits, members of the file's group other than the
owner have permission checked with respect to the ``group''
mode bits, and all others have permissions checked with re-
spect to the ``other'' mode bits.
Note the "members of the file's group _other_than_the_owner_" and the
implicit similar exception in the "other". This reads precisely as
David would have it.
--
Lucio de Re (lucio@proxima.alt.za)
Disclaimer: I'm working at getting my opinions to agree with me.
next reply other threads:[~1997-09-15 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-15 15:15 Lucio [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-15 19:33 G.David
1997-09-15 17:59 rsc
1997-09-15 15:18 G.David
1997-09-15 14:38 G.David
1997-09-15 14:26 rsc
1997-09-15 14:22 Lucio
1997-09-15 13:52 rsc
1997-09-15 13:28 G.David
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=19970915151513.wCAn03L-dbh_Z5u4crRiWMLddzrsJ6HZuJXVIVKc2Ew@z \
--to=9fans@9fans.net \
/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).