All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Bill Johnstone <beejstone3@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Configuration for NFSv3 only?
Date: Tue, 26 Jul 2005 08:52:15 -0400	[thread overview]
Message-ID: <42E631FF.3050005@redhat.com> (raw)
In-Reply-To: <20050725223530.80613.qmail@web33915.mail.mud.yahoo.com>

Bill Johnstone wrote:

>--- Peter Staubach <staubach@redhat.com> wrote:
>
>  
>
>>The answer to this question is that the portmapper protocol is
>>completely
>>separate from the NFS and related protocols such as nlockmgr and
>>mountd.
>>
>>There are newer versions of the protocol, 10000, which are now called
>>
>>rpcbind.
>>
>>But, the short answer, is that portmapper, version 2, is fine for
>>these 
>>purposes.
>>    
>>
>
>Does this separation of versions also apply to "status"?  The version
>given for that both on the client and server sides is "1".
>
>Is that OK for NFSv3 operation?
>

Hi.

Yes, version 1 for the status protocol is also fine and is not related 
to the
version of NFS, either 2 or 3, being used.  The NFS version 4 protocol is
self contained and does not use either the nlockmgr (network lock manager),
the mount, or the status protocols as part of the support required for it.

A little bit of information --

NFS version 2 uses either MOUNT versions 1 or 2.  The difference between
MOUNT version 1 and MOUNT version 2 is the addition of an operation to
retrieve POSIX pathconf information.

NFS version 2 uses either NLOCKMGR versions 1 or 3.  The difference between
versions 1 and 3 is the addition of some primitives for file sharing, ala
DOS.

NFS version 3 uses MOUNT version 3.  This version of the MOUNT protocol is
similar to the MOUNT version 1 protocol, but returns NFS version 3 file
handles instead of NFS version 2 file handles.

NFS version 3 uses NLOCKMGR version 4.  This version of the NLOCKMGR
protocol is similar to the NLOCKMGR version 3 protocol, but assumes that
the owner handle encapsulates an NFS version 3 file handle instead of an
NFS version 2 filehandle.

You might also notice two versions of a protocol called NFS_ACL.  This
protocol was designed in order to handle POSIX style ACLs.  It also
contains some extensions to handle generalized extended attributes.
In the marketplace, certain implementations of NFS version 2 will also
support NFS_ACL version 2.  Certain implementations of NFS version 3
will also support NFS_ACL version 3.  The corresponding version of NFS
uses the corresponding version of the NFS_ACL protocol.

There is support for the NFS_ACL version 3 protocol available in some
versions of Linux.

--

I hope that this is helpful.

       ps


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-07-26 12:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 20:40 Configuration for NFSv3 only? Bill Johnstone
2005-07-25 20:51 ` Trond Myklebust
2005-07-25 21:17   ` Bill Johnstone
2005-07-25 21:27     ` Trond Myklebust
2005-07-25 22:30       ` Bill Johnstone
2005-07-25 23:38         ` Trond Myklebust
2005-07-26  3:55           ` Bill Johnstone
2005-07-26 15:25             ` Trond Myklebust
2005-07-26 22:52               ` Bill Johnstone
2005-07-27  0:32                 ` Trond Myklebust
2005-07-25 22:32       ` Bill Johnstone
2005-07-25 21:47 ` Peter Staubach
2005-07-25 22:35   ` Bill Johnstone
2005-07-26 12:52     ` Peter Staubach [this message]
2005-07-26 22:48       ` Bill Johnstone

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=42E631FF.3050005@redhat.com \
    --to=staubach@redhat.com \
    --cc=beejstone3@yahoo.com \
    --cc=nfs@lists.sourceforge.net \
    /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.