> > 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
