From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 21 Oct 2010 07:08:30 -0400
To: 9fans@9fans.net
Message-ID: <cd8498f888409a5453810fd70cd59b5c@plug.quanstro.net>
In-Reply-To: <621112A569DAE948AD25CCDCF1C07533299A09@dolly.ntdom.cupdx>
References: <9c855ecc7b4384e9a3ecb9ca2416ecac@plan9.bell-labs.com>
	<AANLkTiktMPG7H_q36bYddECEZ+T9o1g3RaEgnu5tBXXd@mail.gmail.com>
	<621112A569DAE948AD25CCDCF1C07533299A08@dolly.ntdom.cupdx>
	<76680b2c03af6f1e1efac67fe8d2e590@ladd.quanstro.net>
	<621112A569DAE948AD25CCDCF1C07533299A09@dolly.ntdom.cupdx>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] sheevaplug port available
Topicbox-Message-UUID: 6bd82c10-ead6-11e9-9d60-3106f5b1d025

> This is on a combined CPU/auth server, and was run as the hostowner (bootes).
> Are the permissions wrong out-of-the-box?  Could this be because some directories
> are owned by sys while others by bootes?  bootes is a member of the sys group, but
> as we discussed previously, that won't be honored in the current implementation.

this is almost certainly incorrect.  (you don't mention you're using 9vx' #Z.)
plan 9 fileservers that store files on disk (fossil, kfs, kenfs, cwfs, etc) do
maintain their own groups.  you may wish to put your fs into allow mode
for pull.

it's plan 9 file servers living in the local kernel, e.g. #c, that don't know about
groups.

- erik