linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jim Rees <rees@umich.edu>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: please proof-read: updates to nfs.man for some missing options.
Date: Thu, 14 Nov 2013 14:25:56 +1100	[thread overview]
Message-ID: <20131114142556.41724d1b@notabene.brown> (raw)
In-Reply-To: <1AF110D7-1CE6-491B-85C6-F6A2692F93B6@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

On Wed, 13 Nov 2013 22:13:56 -0500 Chuck Lever <chuck.lever@oracle.com> wrote:

> 
> On Nov 13, 2013, at 10:12 PM, Jim Rees <rees@umich.edu> wrote:
> 
> > NeilBrown wrote:
> > 
> >  +.BR addr= ip-address
> >  +This option is rarely used but can provide an explicit IP address of
> >  +the NFS server in cases where the server is multi-homed.
> >  +.TP 1.5i
> > 
> > I would change "rarely used" to "usually not needed." Also I think you have
> > this option in here twice.

Yes I included it twice.  Once for v2+v3, once for "v4".  There are a few
other options that are given for bother rather than in the common section and
this seemed to fit better with those.

> 
> I actually think mount.nfs may strip this option out of the list if a user specifies it.
> 

Indeed it does.  Well, I can scrape that then - thanks.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2013-11-14  4:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14  3:02 please proof-read: updates to nfs.man for some missing options NeilBrown
2013-11-14  3:11 ` Chuck Lever
2013-11-14  3:33   ` NeilBrown
2013-11-14  3:12 ` Jim Rees
2013-11-14  3:13   ` Chuck Lever
2013-11-14  3:25     ` NeilBrown [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=20131114142556.41724d1b@notabene.brown \
    --to=neilb@suse.de \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@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).