From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ownership settings on a second KFS
Date: Mon, 9 Sep 2002 13:46:40 -0400 [thread overview]
Message-ID: <06f1ad52e5ad37b3c402aae3d5cdfb79@centurytel.net> (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.
Although it would make sense because of uniformity (why should the
first disk be any different to kfs than the second, etc.) notice that
I didn't say I liked it ☺
>
>> 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.
>
I miss typed. I meant to say "does NOT".
next reply other threads:[~2002-09-09 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 17:46 Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-09 20:52 Russ Cox
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=06f1ad52e5ad37b3c402aae3d5cdfb79@centurytel.net \
--to=fst@centurytel.net \
--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).