linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
	NFS maillist <nfs@lists.sourceforge.net>,
	nfsv4-wg@citi.umich.edu
Subject: Re: [NFS] [PATCH 20/19] A basic NFSv4 client for 2.5.x
Date: 15 Oct 2002 00:46:25 +0200	[thread overview]
Message-ID: <shsk7kkljum.fsf@charged.uio.no> (raw)
In-Reply-To: <15787.18187.306840.862917@charged.uio.no>

>>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

     > This patch defines a new switch in fs/Config.in -
     >   CONFIG_NFS_V4: enables nfsv4 client

Please note: for those who are interested in trying this out, a patch
for the 'mount' program in util-linux-2.11r is available on

  http://www.fys.uio.no/~trondmy/src/NFSv4/mount-2.11r-nfsv4.patch

Note however that the NFS client is not yet fully functional, as it
lacks the upcall + RPCSEC_GSS. These features are forthcoming...

Cheers,
  Trond

           reply	other threads:[~2002-10-14 22:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <15787.18187.306840.862917@charged.uio.no>]

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=shsk7kkljum.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4-wg@citi.umich.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;
as well as URLs for NNTP newsgroup(s).