9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] group permission
Date: Mon, 31 Jul 2006 06:18:26 +0900	[thread overview]
Message-ID: <69081255-C87C-41C0-AA0A-3091DA3D8C9C@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <ee9e417a0607301239s1c6bd879x582c3dccf44f5a52@mail.gmail.com>

Russ's solution solves most popular case that arises in human group
working.
However allowing chgrp without editing /adm/users will solve
different problem.
Suppose bob is a teacher and he is teaching something to alice and
carol.
Alice want to show her files to only bob, and carol also want to show
her files only to bob.
How to do that ?
Creating new group does not answer the purpose.
The only solution of current Plan 9 is
	chgrp bob ...
by host owner.

My question comes from real problem.
bob is a service program.
alice and carol are system users.

Kenji Arisawa

On 2006/07/31, at 4:39, Russ Cox wrote:

> This isn't limited to just this one case.
> According to the documentation, a group owner
> has the ability to add or remove people from a group,
> but actually there is no interface for doing so.
>
> The right solution is probably a way to talk to a file
> server to create a new group (owned by the
> user who created it) and also to edit existing groups,
> subject to the documented permissions.
>
> Russ



  reply	other threads:[~2006-07-30 21:18 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 [this message]
2006-07-30 22:07     ` Russ Cox
2006-07-30 22:12       ` Rob Pike
2006-07-31  3:35       ` Skip Tavakkolian
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=69081255-C87C-41C0-AA0A-3091DA3D8C9C@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --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).