Updates to nfsroot documentation
Subsystems (4)
PATCH 1/4 Updates to nfsroot documentation
From: Amos Waterland <[email protected]>
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.
Signed-off-by Amos Waterland <[email protected]>
Cc Simon Horman <[email protected]>
Cc Andi Kleen <[email protected]>
Cc "David S. Miller" <[email protected]>
Signed-off-by Andrew Morton <[email protected]>
---
Documentation/nfsroot.txt | 12 +++++++++--- net/ipv4/ipconfig.c | 20 +------------------- 2 files changed, 10 insertions(+), 22 deletions(-)
Documentation/nfsroot.txt renamed from Documentation/nfsroot.txt~updates-to-nfsroot-documentation-take-3 +9 -3
@@ -92,8 +92,14 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netm 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. The most common way to use this + is "ip=dhcp". + + 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 +148,7 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netm 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
net/ipv4/ipconfig.c renamed from net/ipv4/ipconfig.c~updates-to-nfsroot-documentation-take-3 +1 -19
@@ -1410,25 +1410,7 @@ late_initcall(ip_auto_config);/* * Decode any IP configuration options in the "ip=" or "nfsaddrs=" kernel -* command line parameter. It consists of option fields separated by colons in -* the following order: -* -* <client-ip>:<server-ip>:<gw-ip>:<netmask>:<host name>:<device>:<PROTO> -* -* Any of the fields can be empty which means to use a default value: -* <client-ip> - address given by BOOTP or RARP -* <server-ip> - address of host returning BOOTP or RARP packet -* <gw-ip> - none, or the address returned by BOOTP -* <netmask> - automatically determined from <client-ip>, or the -* one returned by BOOTP -* <host name> - <client-ip> in ASCII notation, or the name returned -* by BOOTP -* <device> - use all available devices -* <PROTO>: -* off|none - don't do autoconfig at all (DEFAULT) -* on|any - use any configured protocol -* dhcp|bootp|rarp - use only the specified protocol -* both - use both BOOTP and RARP (not DHCP) +* command line parameter. See Documentation/nfsroot.txt. */ static int __init ic_proto_name (char *name) {
_
From: [email protected]
Date: Thu, 13 Dec 2007 16:02:33 -0800
Quoted 7 lines
From: Amos Waterland <[email protected]>
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.
Quoted 5 lines
Signed-off-by Amos Waterland <[email protected]>Cc Simon Horman <[email protected]>Cc Andi Kleen <[email protected]>Cc "David S. Miller" <[email protected]>Signed-off-by Andrew Morton <[email protected]>
Applied.