From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: jstrand1@rochester.rr.com (James D Strandboge)
Cc: LINUX-KERNEL <linux-kernel@vger.kernel.org>
Subject: Re: status of nfs and tcp with 2.4
Date: 27 Sep 2001 17:32:09 +0200 [thread overview]
Message-ID: <shssnd88xae.fsf@charged.uio.no> (raw)
In-Reply-To: <20010927105321.A15128@rochester.rr.com>
In-Reply-To: jstrand1@rochester.rr.com's message of "Thu, 27 Sep 2001 10:53:21 -0400"
>>>>> " " == James D Strandboge <jstrand1@rochester.rr.com> writes:
> What is the status of tcp and nfs with the 2.4 kernel? The
> sourceforge site (regarding this) has not changed for a while
> and the NFS FAQ at sourceforge simply states: nfsv3 over tcp
> does not work - the code for 2.4.x is as yet to be merged
> What progress is being made toward this end?
None: AFAIK nobody has yet written any code that works for the server.
The client works though...
Cheers,
Trond
next prev parent reply other threads:[~2001-09-27 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 14:53 status of nfs and tcp with 2.4 James D Strandboge
2001-09-27 15:32 ` Trond Myklebust [this message]
2001-09-27 17:10 ` James D Strandboge
2001-09-27 17:27 ` Bill Rugolsky Jr.
2001-09-28 8:46 ` Trond Myklebust
2001-10-03 12:33 ` James D Strandboge
2001-10-03 14:31 ` Trond Myklebust
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=shssnd88xae.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=jstrand1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
/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