All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartmut Niemann <Hartmut.Niemann@gmx.de>
To: Simon Horman <horms@verge.net.au>
Cc: linux-kernel@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP must be set
Date: Mon, 27 Oct 2008 22:41:14 +0100	[thread overview]
Message-ID: <200810272241.14531.Hartmut.Niemann@gmx.de> (raw)
In-Reply-To: <20081027052409.GC6818@verge.net.au>

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@gmx.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.


  reply	other threads:[~2008-10-27 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 21:47 nfsroot.txt in 2.4.36.7 and 2.6.27.1, Configure.help in 2.4.36.7: missing precondition CONFIG_IP_PNP Hartmut Niemann
2008-10-26  3:27 ` Willy Tarreau
2008-10-26 12:06   ` Hartmut Niemann
2008-10-27  5:24 ` Simon Horman
2008-10-27 21:41   ` Hartmut Niemann [this message]
2008-10-27 22:04     ` [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP must be set Matthias Schniedermeyer

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=200810272241.14531.Hartmut.Niemann@gmx.de \
    --to=hartmut.niemann@gmx.de \
    --cc=Trond.Myklebust@netapp.com \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.