From: Kenji Arisawa arisawa@vega.aichi-u.ac.jp
Subject: [9fans] group organization
Date: Fri, 24 Oct 1997 00:45:11 +0900 [thread overview]
Message-ID: <19971023154511.XtS__W3PKcBONCqUIie0sniQ_HIepVet7veCAQkVrf0@z> (raw)
Hello 9fans!
>From: David Butler <gdb@dbSystems.com>
>I've been thinking of how to allow network access to the file server
>besides the "connect a serial cable to a cpu server and use consolefs".
>Perhaps a file like /adm/cons which provides read/write access to the
>console thread. Then you put users in the adm group with read/write
>group perms on /adm/cons to get to it. Comments?
That may be a good idea. I will try it.
By the way, I have another question on the group organization.
Plan9 forbids:
chgrp group file ...
to the group the user does not belong to.
I cannot understand this restriction.
What problem does it make if plan9 admits:
chgrp anygroup file ...
Here is an example that shows this effect.
Let /adm/users be
alice:alice
bob:bob:
david:david:
and david be a professional programmer who is advising both alice and bob.
Assume alice doesn't want to be read her file to bob and
bob also doesn't want to be read his file to alice.
Then if alice and bob could execute respectively,
alice% chgrp david herfile; chmod 640 herfile
bob% chgrp david hisfile; chmod 640 hisfile
everything would go well!
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~1997-10-23 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 15:45 Kenji [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-24 4:30 G.David
1997-10-24 4:00 Scott
1997-10-24 3:26 G.David
1997-10-24 0:22 Scott
1997-10-23 23:45 G.David
1997-10-22 15:49 G.David
1997-10-22 7:10 Kenji
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=19971023154511.XtS__W3PKcBONCqUIie0sniQ_HIepVet7veCAQkVrf0@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).