From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] Plan9 permissions
Date: Mon, 15 Sep 1997 16:22:09 +0200 [thread overview]
Message-ID: <19970915142209.DcbkmYPT-yAbP4Wf1SwO_7Wu8kM-UCtfycNLgse1FZs@z> (raw)
>
> if you are the owner and the permissions are
> something like 466, then you can just change them
> with chmod. if you are in the group and the
> permissions are something like 446 or 646, then
> you can just become none (echo -n none >/dev/user)
> and then you have permission again.
>
And yet, David has a point. I remember my first confrontation with the
description of permissions, and it seemed equally silly. But in
practice the owner may prefer to be reminded not to alter the contents
of a file that a log process is allowed to update.
Note, as David says, that the more obvious approach has no mechanism to
stop the owner doing anything if anyone else can do it. In such a
situation, a 446 permission serves no useful purpose.
--
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 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-15 14:22 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 15:15 Lucio
1997-09-15 14:38 G.David
1997-09-15 14:26 rsc
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=19970915142209.DcbkmYPT-yAbP4Wf1SwO_7Wu8kM-UCtfycNLgse1FZs@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).