From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] group permission
Date: Sun, 30 Jul 2006 20:35:10 -0700 [thread overview]
Message-ID: <cb496f26360c248d93c303dc27546077@9netics.com> (raw)
In-Reply-To: <ee9e417a0607301507w53ab74fck63d356b36c04ebcb@mail.gmail.com>
*if* /srv handled group permissions some of these use cases could be
done through /srv, couldn't it?
an old discussion where pressoto and nemo outlined the problem:
(btw, has pressoto disowned 9fans?)
http://groups.google.com/group/comp.os.plan9/browse_thread/thread/846148c4df8ea674/9fe6dabdb7a7edb4?lnk=gst&q=group+permissions+on+%2Fsrv&rnum=1#9fe6dabdb7a7edb4
> other defined permission and mode bits can. The gid can be
> changed: by the owner if also a member of the new group; or
> by the group leader of the file's current group if also
> leader of the new group (see intro(9P) for more information
> about permissions, users, and groups). None of the other
>
> I don't think anything terrible would happen if
> one deleted the text "if also a member of the new group"
> for the owner. Maybe it's a holdover from Unix worth
> getting rid of. It's almost certainly a one-line change
> to fossil.
next prev parent reply other threads:[~2006-07-31 3:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 12:47 arisawa
2006-07-30 13:06 ` Sascha Retzki
2006-07-30 15:40 ` Skip Tavakkolian
2006-07-30 18:25 ` csant
2006-07-30 19:39 ` Russ Cox
2006-07-30 21:18 ` arisawa
2006-07-30 22:07 ` Russ Cox
2006-07-30 22:12 ` Rob Pike
2006-07-31 3:35 ` Skip Tavakkolian [this message]
2006-07-31 14:37 ` Russ Cox
2006-07-31 22:17 ` arisawa
2006-07-31 15:04 ` Victor Nazarov
2006-07-31 15:34 ` Wes Kussmaul
2006-07-31 20:37 Sascha Retzki
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=cb496f26360c248d93c303dc27546077@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
/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).