From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] none attaches a fs
Date: Thu, 26 Sep 2002 08:37:07 -0400 [thread overview]
Message-ID: <7c8f85adcb814481d3e48d704602489b@plan9.bell-labs.com> (raw)
> Is there a reason that the behaviour of fs(4) is different
> from that of kfs? kfs's treating of none looks more
> reasonable to me.
Fs and kfs diverged long ago. The kfs network policy is
more tuned to being in an untrusted environment, whereas
fs just isn't. There's no particular reason, except that
kfs has been used in a few untrusted environments, so it
picked up these things. Some day we'll have only one file
server.
Russ
next reply other threads:[~2002-09-26 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 12:37 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 8:10 YAMANASHI Takeshi
2002-10-02 7:58 Fco.J.Ballesteros
2002-10-02 7:41 YAMANASHI Takeshi
2002-09-26 6:07 YAMANASHI Takeshi
2002-09-25 14:23 Russ Cox
2002-09-25 5:56 YAMANASHI Takeshi
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=7c8f85adcb814481d3e48d704602489b@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).