From: Dax Kelson <dax@gurulabs.com>
To: linux-kernel@vger.kernel.org
Subject: Anyone using NFSv4?
Date: 18 Jun 2002 22:59:41 -0600 [thread overview]
Message-ID: <1024462781.17191.18.camel@thud> (raw)
In-Reply-To: <008001c216c8$d0bfdba0$294b82ce@connecttech.com>
I noticed that the CITI group release a new June snapshot of NFSv4
support for Linux. It is a patch against 2.4.18.
http://www.citi.umich.edu/projects/nfsv4/june_2002_rel/index.html
They say, "The current version passes all Connectathon tests, and
interoperates with other implementations".
Currently NFSv2/3 is too insecure for my tastes, I'm greatly looking
forward to the strong authentication, integrity, and privacy that NFSv4
with secure RPC offers. I can envision handy uses for the "pseudo path"
feature of NFSv4 as well.
I was just wondering if anyone (other that CITI) is keeping an eye on
it? Are there any pieces worth merging yet? Just curious.
Dax Kelson
next prev parent reply other threads:[~2002-06-19 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 17:27 n_tty.c driver patch (semantic and performance correction) (a ll recent versions) Ed Vance
2002-06-18 2:00 ` Robert White
2002-06-18 13:05 ` Stuart MacDonald
2002-06-19 4:59 ` Dax Kelson [this message]
2002-06-19 23:48 ` Anyone using NFSv4? David Ford
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=1024462781.17191.18.camel@thud \
--to=dax@gurulabs.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