From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <876a8b7b9733e7f1321f06c5110772ae@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 28 Jan 2008 15:33:23 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the meaning of group
In-Reply-To: <47cc64d677664707853d557dd42d22ed@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 3c3069c6-ead3-11e9-9d60-3106f5b1d025

> 
> it's just the same: is the user a member of a given group or not?
> how membership is established is up to the file server.
> the kernel's scheme is trivial (although it could be more elaborate)
> but that doesn't limit what other file servers do.
> as with the examples you mention, they have only to implement it.
> 

explain how it could be more elaborate.  where do you put the mapping.
the auth server?

as far as i can tell, unless a kernel-generated file has permissions like 0064,
and the owner is eve, the group checking in the kernel doesn't do anything.

i should explain a bit the context.  since we have many folks with a use
for the aoe device on a few cpu servers, it would be useful to allow, say,
the fileserver group sys access to /dev/aoe/*.

- erik