From: Matthias Schniedermeyer <ms@citd.de>
To: Hartmut Niemann <Hartmut.Niemann@gmx.de>
Cc: Simon Horman <horms@verge.net.au>,
linux-kernel@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: Re: [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP must be set
Date: Mon, 27 Oct 2008 23:04:19 +0100 [thread overview]
Message-ID: <20081027220419.GA12618@citd.de> (raw)
In-Reply-To: <200810272241.14531.Hartmut.Niemann@gmx.de>
On 27.10.2008 22:41, Hartmut Niemann wrote:
> 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).
Technically you neither need autoconfiguration nor CONFIG_ROOT_NFS.
With an initrd/initramfs you can do the whole procedure from userspace.
And AFAIR a few years back those options where on the brink of beeing
deprecated for just that reason.
Just my 2 cents.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
prev parent reply other threads:[~2008-10-27 22:04 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 ` [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP must be set Hartmut Niemann
2008-10-27 22:04 ` Matthias Schniedermeyer [this message]
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=20081027220419.GA12618@citd.de \
--to=ms@citd.de \
--cc=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.