From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
Frank van Maarseveen <frankvm@xs4all.nl>,
Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: userspace NFS daemon
Date: Tue, 7 Sep 2004 12:40:47 +0200 [thread overview]
Message-ID: <20040907104047.GA11764@suse.de> (raw)
In-Reply-To: <1094441577.10492.134.camel@lade.trondhjem.org>
On Sun, Sep 05, 2004 at 11:32:57PM -0400, Trond Myklebust wrote:
> No. I mean that very few people have ever used unfsd in mission-critical
> production environments.
> You might get away with it for read-only stuff (if you are prepared to
> put up with the speed), but nobody should be using it for read/write
> partitions.
Suse actually used it for /home until about 1.5 years ago or even
less, and we had less problems than with knfsd.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-09-07 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 21:09 userspace NFS daemon Frank van Maarseveen
2004-09-05 21:25 ` Trond Myklebust
2004-09-05 22:01 ` Frank van Maarseveen
2004-09-05 22:10 ` Trond Myklebust
2004-09-06 0:47 ` Bogdan Costescu
2004-09-06 3:32 ` Trond Myklebust
2004-09-06 19:35 ` Bogdan Costescu
2004-09-06 20:08 ` Trond Myklebust
2004-09-07 10:40 ` Olaf Kirch [this message]
2004-09-06 7:41 ` Peter Astrand
2004-09-06 19:13 ` Frank van Maarseveen
2004-09-06 19:43 ` Peter Astrand
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=20040907104047.GA11764@suse.de \
--to=okir@suse.de \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=frankvm@xs4all.nl \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.