9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9nfs
Date: Fri, 10 Oct 2003 09:54:49 +0900	[thread overview]
Message-ID: <4e4885b610c6452da4c7d2ac9c981bc4@orthanc.cc.titech.ac.jp> (raw)

On Fri Oct 10 09:35:37 JST 2003, matt@proweb.co.uk wrote:
> Before I start the long journey does anyone have any insight into how
> well plan9 behaves as an nfs server.

i think 9nfs behaves very well because nfsserver(8) says:

     DESCRIPTION
          ........  All
          users on client machines have the access privileges of the
          Plan 9 user `none'.
           :
     BUGS
          It would be nice to provide authentication for users, but
          Unix systems provide too low a level of security to be
          trusted in a Plan 9 world.

but this behaviour could be considered bad for your purpose.
--




             reply	other threads:[~2003-10-10  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10  0:54 YAMANASHI Takeshi [this message]
2003-10-10  1:38 matt
2003-10-10  0:10 ` Russ Cox

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=4e4885b610c6452da4c7d2ac9c981bc4@orthanc.cc.titech.ac.jp \
    --to=uncover@beat.cc.titech.ac.jp \
    --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).