From: David Ford <david+cert@blue-labs.org>
To: Dax Kelson <dax@gurulabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anyone using NFSv4?
Date: Wed, 19 Jun 2002 19:48:16 -0400 [thread overview]
Message-ID: <3D111840.30605@blue-labs.org> (raw)
In-Reply-To: 1024462781.17191.18.camel@thud
My first glance at it suggested that only ext2/ext3 filesystems were
supported. I run all reiserfs so I'l have to wait.
David
Dax Kelson wrote:
>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
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
prev parent reply other threads:[~2002-06-19 23:48 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 ` Anyone using NFSv4? Dax Kelson
2002-06-19 23:48 ` David Ford [this message]
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=3D111840.30605@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=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