9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] group ownership for shared devices
Date: Mon,  9 Nov 2009 22:00:18 -0800	[thread overview]
Message-ID: <dd6fe68a0911092200j33c60239s577a336a5dd0ce11@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.00.0911092236430.42237@legolas.yyc.orthanc.ca>

On Mon, Nov 9, 2009 at 9:44 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> I have a CPU server running as 'glenda' that has a DVD drive. I want to make
> that DVD drive available to various terminals on the network. But I don't
> want to put the terminal users into glenda's group. The obvious
> solution seemed to be to set up a 'commondevs' group, add glenda and the
> allowed device users to it, then have the CPU server 'chgrp commondevs
> /dev/...' but no joy there. There's got to be something stunningly simple
> here that I'm missing ...

This solution didn't work because groups are specific to the
file server implementing them.  Your CPU server doesn't know
about the groups on your file servers and doesn't itself
implement any groups.

You could hack up a copy of srvfs that looks at the user
name being presented over the 9P connection and makes
the decision that way, or you could write a custom file server
with its own group list, like consolefs has.

Russ


  reply	other threads:[~2009-11-10  6:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  5:44 Lyndon Nerenberg
2009-11-10  6:00 ` Russ Cox [this message]
2009-11-10  6:24   ` Lyndon Nerenberg
2009-11-10  7:20   ` Lyndon Nerenberg
2009-11-10 13:22 José Brandão
     [not found] <<a4d96da30911100522w825d264v56bf72fd3f99385c@mail.gmail.com>
2009-11-10 13:58 ` erik quanstrom
2009-11-10 15:27 José Brandão

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=dd6fe68a0911092200j33c60239s577a336a5dd0ce11@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=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).