From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dax Kelson <dax@gurulabs.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Kendrick M. Smith" <kmsmith@umich.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>,
beepy@netapp.com, trond.myklebust@fys.uio.no,
torvalds@transmeta.com
Subject: Re: Will NFSv4 be accepted?
Date: Thu, 15 Aug 2002 00:07:13 -0400 [thread overview]
Message-ID: <20020815040713.GA18419@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208141938350.31203-100000@mooru.gurulabs.com>
On Wed, Aug 14, 2002 at 07:51:56PM -0600, Dax Kelson wrote:
> Right, I do understand that Kerberized/GSS NFS is not exclusive to NFSv4.
> However, right now, there is only one way to get Kerberized NFS. The CITI
> NFSv4 patches.
>
> Those patches are, in their estimation, ready for inclusion. NFSv3
> support is "coming down the pipeline".
The minimal NFSv4 patches which Kendrick has submitted are ready for
inclusion, but those do not include rpcsec_gss support. The only
patches which include rpcsec_gss support are patches against 2.4.18, and
they aren't in good enough shape yet, though we hope they will be soon!
--Bruce F.
next prev parent reply other threads:[~2002-08-15 4:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 23:01 patch 14/38: CLIENT: add ->setup_read() nfs_rpc_op for async read, part 1 Kendrick M. Smith
2002-08-13 23:01 ` Kendrick M. Smith
2002-08-14 20:49 ` Will NFSv4 be accepted? Dax Kelson
2002-08-14 20:49 ` Dax Kelson
2002-08-14 22:17 ` Trond Myklebust
2002-08-14 22:17 ` Trond Myklebust
2002-08-14 22:34 ` Brian Pawlowski
2002-08-14 22:34 ` [NFS] " Brian Pawlowski
2002-08-14 23:21 ` Alexander Viro
2002-08-14 23:21 ` [NFS] " Alexander Viro
2002-08-15 1:10 ` Alan Cox
2002-08-15 6:18 ` marius aamodt eriksen
2002-08-15 6:18 ` [NFS] " marius aamodt eriksen
2002-08-15 11:08 ` Alan Cox
2002-08-15 11:08 ` [NFS] " Alan Cox
2002-08-15 1:10 ` Alan Cox
2002-08-15 6:23 ` marius aamodt eriksen
2002-08-15 6:23 ` [NFS] " marius aamodt eriksen
2002-08-15 14:19 ` Trond Myklebust
2002-08-15 14:19 ` Trond Myklebust
2002-08-15 1:09 ` Alan Cox
2002-08-15 1:27 ` Dax Kelson
2002-08-15 1:27 ` Dax Kelson
2002-08-15 1:35 ` Alan Cox
2002-08-15 1:35 ` Alan Cox
2002-08-15 1:51 ` Dax Kelson
2002-08-15 1:51 ` Dax Kelson
2002-08-15 4:07 ` J. Bruce Fields
2002-08-15 4:07 ` J. Bruce Fields [this message]
2002-08-15 17:35 ` Linus Torvalds
2002-08-15 17:35 ` Linus Torvalds
2002-08-15 18:20 ` Dax Kelson
2002-08-15 18:20 ` Dax Kelson
2002-08-15 19:52 ` Roger Luethi
2002-08-15 19:52 ` Roger Luethi
2002-08-15 23:07 ` Trond Myklebust
2002-08-15 23:07 ` Trond Myklebust
2002-08-16 14:54 ` Oliver Xymoron
2002-08-16 19:44 ` Linus Torvalds
2002-08-15 1:09 ` Alan Cox
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=20020815040713.GA18419@fieldses.org \
--to=bfields@fieldses.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=beepy@netapp.com \
--cc=dax@gurulabs.com \
--cc=kmsmith@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=torvalds@transmeta.com \
--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.