linux-kernel - [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200810272241.14531.Hartmut.Niemann@gmx.de>
Date:	Mon, 27 Oct 2008 22:41:14 +0100
From:	Hartmut Niemann <Hartmut.Niemann@....de>
To:	Simon Horman <horms@...ge.net.au>
Cc:	linux-kernel@...r.kernel.org, Trond.Myklebust@...app.com
Subject: [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP must be set

The file nfsroot.txt fails to mention, that Kernel level autoconfiguration 
CONFIG_IP_PNP must be selected in order to be able to even see
the option "Root file system on NFS" (CONFIG_ROOT_NFS)

I reordered the section 1 of nfsroot.txt and emphasized the dependency.
(And I fixed some chapter numbering in section 3).

Signed-off-by: Hartmut Niemann <Hartmut.Niemann@....de>
---
--- linux-2.6.27.1/Documentation/filesystems/nfsroot.txt        2008-10-16 
01:02:53.000000000 +0200
+++ linux-2.6.27.1-HN/Documentation/filesystems/nfsroot.txt     2008-10-25 
23:24:48.000000000 +0200
@@ -22,15 +22,13 @@
 1.) Enabling nfsroot capabilities
     -----------------------------

-In order to use nfsroot, NFS client support needs to be selected as
-built-in during configuration. Once this has been selected, the nfsroot
-option will become available, which should also be selected.
-
-In the networking options, kernel level autoconfiguration can be selected,
-along with the types of autoconfiguration to support. Selecting all of
-DHCP, BOOTP and RARP is safe.
-
-
+In order to use nfsroot, in the networking options,  IP kernel level
+autoconfiguration must be selected, along with the types of autoconfiguration
+to support. Selecting all of DHCP, BOOTP and RARP is safe.
+
+Then NFS client support needs to be selected as built-in during
+configuration. Once this has been selected, the nfsroot option will become
+available, which must also be selected.


 2.) Kernel command line
@@ -207,7 +205,7 @@
        For more information on isolinux, including how to create bootdisks
        for prebuilt kernels, see http://syslinux.zytor.com/

-3.2) Using LILO
+3.3) Using LILO
        When using LILO all the necessary command line parameters may be
        specified using the 'append=' directive in the LILO configuration
        file.
@@ -219,11 +217,11 @@

        For information on configuring LILO, please refer to its 
documentation.

-3.3) Using GRUB
+3.4) Using GRUB
        When using GRUB, kernel parameter are simply appended after the kernel
        specification: kernel <kernel> <parameters>

-3.4) Using loadlin
+3.5) Using loadlin
        loadlin may be used to boot Linux from a DOS command prompt without
        requiring a local hard disk to mount as root. This has not been
        thoroughly tested by the authors of this document, but in general
@@ -232,7 +230,7 @@

        Please refer to the loadlin documentation for further information.

-3.5) Using a boot ROM
+3.6) Using a boot ROM
        This is probably the most elegant way of booting a diskless client.
        With a boot ROM the kernel is loaded using the TFTP protocol. The
        authors of this document are not aware of any no commercial boot
@@ -241,7 +239,7 @@
        etherboot, both of which are available on sunsite.unc.edu, and both
        of which contain everything you need to boot a diskless Linux client.

-3.6) Using pxelinux
+3.7) Using pxelinux
        Pxelinux may be used to boot linux using the PXE boot loader
        which is present on many modern network cards.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/