From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7494f610b456eb3af1b33688159ac443@plan9.bell-labs.com>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ownership settings on a second KFS
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon,  9 Sep 2002 16:52:18 -0400
Topicbox-Message-UUID: e7bb2eb0-eaca-11e9-9e20-41e7f4b1d025

> It makes sense that each additional kfs for additional drives will need
> its own /adm/users at the root of the filesystem it handles. Is there a better
> way to supply this other than copying it from the initial kfs at startup?

I don't think so.

> Binding to the first /adm does seem to work.

I think you're imagining that.  Kfs doesn't
know anything about bind, so it can't see the
binding you introduce.

Note that if /adm/users is empty, kfs uses
a default list of

	-1:adm:adm:
	0:none:adm:
	1:tor:tor:
	2:glenda:glenda:
	10000:sys::
	10001:upas:upas:
	10002:bootes:bootes:

Russ