From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ownership settings on a second KFS
Date: Mon, 9 Sep 2002 16:52:18 -0400 [thread overview]
Message-ID: <7494f610b456eb3af1b33688159ac443@plan9.bell-labs.com> (raw)
> 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
next reply other threads:[~2002-09-09 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 20:52 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-09 17:46 Skip Tavakkolian
2002-09-09 17:05 Skip Tavakkolian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7494f610b456eb3af1b33688159ac443@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).