mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Spencer Shepler <shepler@eng.sun.com>
To: Pavel Machek <pavel@suse.cz>
Cc: "Kendrick M. Smith" <kmsmith@umich.edu>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	nfs@lists.sourceforge.net, nfsv4-wg@sunroof.eng.sun.com
Subject: Re: [NFS] Re: NFS version 4 at the University of Michigan
Date: Mon, 11 Feb 2002 04:10:20 -0600	[thread overview]
Message-ID: <20020211041020.E100576@shepler.eng.sun.com> (raw)
In-Reply-To: <Pine.SOL.4.33.0202080036010.1689-100000@rygar.gpcc.itd.umich.edu> <20020209175851.GA113@elf.ucw.cz>
In-Reply-To: <20020209175851.GA113@elf.ucw.cz>

On Sat, Pavel Machek wrote:
> Hi!
> 
> > This is an announcement of the first public release of NFS version 4
> > for Linux, by the University of Michigan.  Up to this point, all of
> > our work has been done privately, but we are now hoping to involve
> > the open-source community at large.  Eventually, we hope to integrate
> > our NFS version 4 implementation into the Linux kernel proper, and
> > find a long-term maintainter for NFS version 4 (possibly one of the
> > current NFS maintainers, possibly one of us working in their spare
> > time).
> 
> Could you sumarise advantages of NFSv4 over v3? Is there usermode
> server for NFSv4? What servers for v4 are known working?

The highlights are:
- NFSv4 allows *nix and windows clients to play well with each other
  (NFSv4/CIFS clients can interact appropriately).
- Strong security (authentication/integrity/privacy) is required of
  implementations.
- A single protocol instead of a collection of protocols (e.g. file
  locking, ACL support are in the protocol)
- Delegation (similar to CIFS oplock support) allows for more
  aggressive caching at the client

The University of Michigan/CITI work is the first to "release" but the
other implementations are not far behind.  We will be meeting at
Connectathon in a couple of weeks to do interoperability testing.
Should be a good event.

-- 
Spencer


      reply	other threads:[~2002-02-11 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 10:21 Kendrick M. Smith
2002-02-09 17:58 ` Pavel Machek
2002-02-11 10:10   ` Spencer Shepler [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=20020211041020.E100576@shepler.eng.sun.com \
    --to=shepler@eng.sun.com \
    --cc=kmsmith@umich.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4-wg@sunroof.eng.sun.com \
    --cc=pavel@suse.cz \
    /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

all inboxes | Powered by JetHome®