From 230e5ab6a084ed50470f101934782dbf54b0d06b Mon Sep 17 00:00:00 2001 From: Ralf Baechle Date: Sat, 6 Dec 1997 23:51:34 +0000 Subject: Merge with Linux 2.1.67. --- Documentation/nfsroot.txt | 52 ++++++++++++++++++++++++++--------------------- 1 file changed, 29 insertions(+), 23 deletions(-) (limited to 'Documentation/nfsroot.txt') diff --git a/Documentation/nfsroot.txt b/Documentation/nfsroot.txt index 43d79a89b..1d42ec6fe 100644 --- a/Documentation/nfsroot.txt +++ b/Documentation/nfsroot.txt @@ -2,6 +2,7 @@ Mounting the root filesystem via NFS (nfsroot) ============================================== Written 1996 by Gero Kuhlmann +Updated 1997 by Martin Mares @@ -47,12 +48,12 @@ root=/dev/nfs nfsroot=[:][,] - If the nfsroot parameter is NOT give on the command line, the default + If the `nfsroot' parameter is NOT given on the command line, the default "/tftpboot/%s" will be used. Specifies the IP address of the NFS server. If this field is not given, the default address as determined by the - nfsaddrs variable (see below) is used. One use of this + `ip' variable (see below) is used. One use of this parameter is for example to allow using different servers for RARP and NFS. Usually you can leave this blank. @@ -76,10 +77,16 @@ nfsroot=[:][,] flags = hard, nointr, noposix, cto, ac -nfsaddrs=:::::: +ip=:::::: - If this parameter is missing on the kernel command line, all fields are - assumed to be empty, and the below mentioned defaults apply. In general + This parameter tells the kernel how to configure IP addresses of devices + and also how to set up the IP routing table. It was originally called `nfsaddrs', + but now the boot-time IP configuration works independently on NFS, so it + was renamed to `ip' and the old name remained as an alias for compatibility + reasons. + + If this parameter is missing from the kernel command line, all fields are + assumed to be empty, and the defaults mentioned below apply. In general this means that the kernel tries to configure everything using both RARP and BOOTP (depending on what has been enabled during kernel confi- guration, and if both what protocol answer got in first). @@ -95,7 +102,7 @@ nfsaddrs=:::::::::::: Netmask for local network interface. If this is empty, - the netmask is derived from the client IP address, un- - less a value has been received by BOOTP. + the netmask is derived from the client IP address assuming + classful addressing, unless overriden in BOOTP reply. Name of the client. If empty, the client IP address is used in ASCII-notation, or the value received by BOOTP. Name of network device to use. If this is empty, all - devices are used for RARP requests, and the first one - found for BOOTP. For NFS the device is used on which - either RARP or BOOTP replies have been received. If - you only have one device you can safely leave this blank. + devices are used for RARP and BOOTP requests, and the + first one we receive a reply on is configured. If you have + only one device, you can safely leave this blank. Method to use for autoconfiguration. If this is either - 'rarp' or 'bootp' the specified protocol is being used. + 'rarp' or 'bootp', the specified protocol is used. If the value is 'both' or empty, both protocols are used so far as they have been enabled during kernel configura- - tion. 'none' means no autoconfiguration. In this case you - have to specify all necessary values in the fields before. + tion. 'off' means no autoconfiguration. - The parameter can appear alone as the value to the nfsaddrs + The parameter can appear alone as the value to the `ip' parameter (without all the ':' characters before) in which case auto- - configuration is used. However, the 'none' value is not available in - that case. + configuration is used. @@ -196,9 +200,11 @@ depend on what facilities are available: 4.) Credits ------- - The nfsroot code in the kernel has been written by me, Gero Kuhlmann - , with the BOOTP code and a couple of bug fixes - contributed by Martin Mares . In order to write - the initial version of nfsroot I would like to thank Jens-Uwe Mager - for his help. + The nfsroot code in the kernel and the RARP support have been written + by Gero Kuhlmann . + + The rest of the IP layer autoconfiguration code has been written + by Martin Mares . + In order to write the initial version of nfsroot I would like to thank + Jens-Uwe Mager for his help. -- cgit v1.2.3