From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <299d2867aa8f8587f6cb67bff55ca368@bellsouth.net>
To: 9fans@9fans.net
Date: Sun, 17 Oct 2010 12:01:55 -0400
From: blstuart@bellsouth.net
In-Reply-To: <621112A569DAE948AD25CCDCF1C075332999FA@dolly.ntdom.cupdx>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] permissions
Topicbox-Message-UUID: 67f81740-ead6-11e9-9d60-3106f5b1d025

>>to elaborate: group permission is not implemented by any
>>kernel file servers in the standard distribution.
>
> And yet, it honors "others" permissions?  I can set the r
> bit on others, and the cat then works...

Right.  Aside from the persistent data file servers, like kfs,
kenfs, and fossil (as Erik mentioned), there's not much that
treats groups in the expected way.  For example, all servers
that use lib9p treat the group as really another user with
privileges that might be different from the world.  So in the
case of a file that's owned by bootes bootes, the group permission
is redundant.  In the case of a file owned by bootes sys,
then bootes gets the owner permission, the *user* sys
gets the group permission and everyone else gets the
world permission.  Take a look at /sys/src/lib9p/uid.c
to see the actual implementation.

BLS