From: Jean-Eric Cuendet <Jean-Eric.Cuendet@linkvest.com>
To: nfs@sourceforge.net
Subject: Re: rpc.mountd + rpc.nfsd
Date: Tue, 03 Sep 2002 08:56:16 +0200 [thread overview]
Message-ID: <3D745D10.4040409@linkvest.com> (raw)
In-Reply-To: 15732.7907.19389.156631@notabene.cse.unsw.edu.au
> The serve different protocols (MOUNTD and NFS). Also mountd runs
OK.
> entirely in user space, nfsd runs entirely in kernel space. It really
> makes sense for them to be separate.
In fact, I thought of a completely userspace daemon. I took
nfs-server-userspace-2.2b47 from the net and wondered why there was 2
daemons while one is IMHO enough.
So, separating things between things that relates is sometimes good, but
sometimes, it add complexity.
Any comment? Why 2 daemons in userspace. And the 2 run as root (I think...)
-jec
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-09-03 6:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 13:12 rpc.mountd + rpc.nfsd Jean-Eric Cuendet
2002-09-03 2:30 ` Neil Brown
2002-09-03 6:56 ` Jean-Eric Cuendet [this message]
2002-09-03 10:18 ` Neil Brown
2002-09-03 10:37 ` Jean-Eric Cuendet
2002-09-03 11:21 ` Neil Brown
2002-09-03 13:45 ` Jean-Eric Cuendet
2002-09-03 14:26 ` David Dougall
2002-09-03 14:36 ` Jean-Eric Cuendet
2002-09-06 1:04 ` Neil Brown
2002-09-04 13:32 ` Jean-Eric Cuendet
2002-09-05 7:19 ` Jean-Eric Cuendet
2002-09-05 12:08 ` Paul Cunningham
2002-09-06 0:59 ` Neil Brown
2002-09-06 6:55 ` Trond Myklebust
2002-09-03 17:01 ` Trond Myklebust
2002-09-04 6:55 ` jbe
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 5:41 Kedar Sovani
2002-09-02 12:52 Jean-Eric Cuendet
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=3D745D10.4040409@linkvest.com \
--to=jean-eric.cuendet@linkvest.com \
--cc=nfs@sourceforge.net \
/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