linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Amos Waterland <apw@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, nico-kernel-nfsroot@schottelius.org
Subject: Re: [PATCH] Updates to nfsroot documentation
Date: Tue, 4 Dec 2007 13:25:47 +0900	[thread overview]
Message-ID: <20071204042545.GA12456@verge.net.au> (raw)
In-Reply-To: <20071204042438.GA11229@verge.net.au>

On Tue, Dec 04, 2007 at 01:24:40PM +0900, Simon Horman wrote:
> On Mon, Dec 03, 2007 at 10:43:45PM -0500, Amos Waterland wrote:
> > The difference between ip=off and ip=::::::off has been a cause of much
> > confusion.  Document how each behaves, and do not contradict ourselves
> > by saying that "off" is the default when in fact "any" is the default
> > and is descibed as being so lower in the file.
> 
> Is that really how it works? If so it sounds a bit silly to me.
> Surely it would be desirable for ip=off and ip=::::::off to
> do the same thing. Or am I missing the point?
> 
> > Signed-off-by: Amos Waterland <apw@us.ibm.com>
> > 
> > ---
> > 
> >  nfsroot.txt |    9 ++++++---
> >  1 file changed, 6 insertions(+), 3 deletions(-)
> > 
> > diff --git a/Documentation/nfsroot.txt b/Documentation/nfsroot.txt
> > index 16a7cae..ac04a1d 100644
> > --- a/Documentation/nfsroot.txt
> > +++ b/Documentation/nfsroot.txt
> > @@ -92,8 +92,11 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
> >    autoconfiguration.
> >  
> >    The <autoconf> parameter can appear alone as the value to the `ip'
> > -  parameter (without all the ':' characters before) in which case auto-
> > -  configuration is used.
> > +  parameter (without all the ':' characters before).  If the value is
> > +  "ip=off" or "ip=none", no autoconfiguration will take place, otherwise
> > +  autoconfiguration will take place.  Note that "ip=off" is not the same
> > +  thing as "ip=::::::off", because in the latter autoconfiguration will take
> > +  place if any of DHCP, BOOTP or RARP are compiled in the kernel.
> >  
> >    <client-ip>	IP address of the client.
> >  
> > @@ -142,7 +145,7 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
> >  		into the kernel will be used, regardless of the value of
> >  		this option.
> >  
> > -                  off or none: don't use autoconfiguration (default)
> > +                  off or none: don't use autoconfiguration
> >  		  on or any:   use any protocol available in the kernel
> >  		  dhcp:        use DHCP
> >  		  bootp:       use BOOTP
> 
> This second fragment seems fine, though perhaps the documentation in
> net/ipv4/ipconfig.c, just above ic_proto_name, should also be updated
> too.

Deleting the documentation in net/ipv4/ipconfig.c might actually
better, as it just duplicates part of what is in Documentation/nfsroot.txt

-- 
Horms


  reply	other threads:[~2007-12-04  4:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04  3:43 [PATCH] Updates to nfsroot documentation Amos Waterland
2007-12-04  4:24 ` Simon Horman
2007-12-04  4:25   ` Simon Horman [this message]
2007-12-04  6:40   ` Amos Waterland

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=20071204042545.GA12456@verge.net.au \
    --to=horms@verge.net.au \
    --cc=apw@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel-nfsroot@schottelius.org \
    /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).