From: David Weinehall <tao@acc.umu.se>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: wnoise@ugcs.caltech.edu, mlist-linux-kernel@nntp-server.caltech.edu
Subject: Re: working userspace nfs v3 for linux?
Date: Thu, 2 Nov 2000 00:59:27 +0100 [thread overview]
Message-ID: <20001102005927.A26355@khan.acc.umu.se> (raw)
In-Reply-To: <linux.kernel.3A008510.FAE271A1@holly-springs.nc.us> <slrn9015t8.u5t.wnoise@barter.ugcs.caltech.edu> <3A00A84E.F3A1C585@holly-springs.nc.us>
In-Reply-To: <3A00A84E.F3A1C585@holly-springs.nc.us>; from rothwell@holly-springs.nc.us on Wed, Nov 01, 2000 at 06:33:34PM -0500
On Wed, Nov 01, 2000 at 06:33:34PM -0500, Michael Rothwell wrote:
> Aaron Denney wrote:
> > I am not aware of any userspace NFSv3 server. Your best bet would
> > probably to take the v2 server and mutate it. Why do you want this beast?
>
> So I can use Linux rather than Solaris 7 and the Solstice Disk Suite,
> which performs like crap thanks to UFS, and the Linux NFS v2
> implementation.
Yes, but why do you need a userspace NFSv3 server? v2.2.18 will contain
knfsdv3, shouldn't this be good enough?
/David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-02 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux.kernel.3A008510.FAE271A1@holly-springs.nc.us>
2000-11-01 22:22 ` Aaron Denney
2000-11-01 23:33 ` Michael Rothwell
2000-11-01 23:59 ` David Weinehall [this message]
2000-11-02 0:01 ` H. Peter Anvin
2000-11-02 17:48 ` working " Michael Rothwell
2000-11-01 19:59 working userspace " Michael Rothwell
2000-11-01 20:52 ` Andi Kleen
2000-11-01 21:03 ` Michael Rothwell
2000-11-02 2:07 ` Horst von Brand
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=20001102005927.A26355@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=mlist-linux-kernel@nntp-server.caltech.edu \
--cc=rothwell@holly-springs.nc.us \
--cc=wnoise@ugcs.caltech.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
all inboxes | Powered by JetHome®