linux-kernel - Re: [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] [day] [month] [year] [list]

Message-ID: <20081027220419.GA12618@citd.de>
Date:	Mon, 27 Oct 2008 23:04:19 +0100
From:	Matthias Schniedermeyer <ms@...d.de>
To:	Hartmut Niemann <Hartmut.Niemann@....de>
Cc:	Simon Horman <horms@...ge.net.au>, linux-kernel@...r.kernel.org,
	Trond.Myklebust@...app.com
Subject: Re: [PATCH] Documentation/filesystems/nfsroot.txt: CONFIG_IP_PNP
	must be set

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.

--
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/