linux-kernel - Re: Multiple ip= boot arguments?

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: <45BE90D4.1030506@zytor.com>
Date:	Mon, 29 Jan 2007 16:27:00 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Chris Friesen <cfriesen@...tel.com>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Kevin Nicoll <blort128@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Multiple ip= boot arguments?

Chris Friesen wrote:
> H. Peter Anvin wrote:
>> Jan Engelhardt wrote:
>>>
>>>> or if I'm supposed to use a startup script instead.
>>>
>>> This is the preffered way nowadays. One day, hopefully,
>>> CONFIG_IP_PNP can go away.
>>>
>> It could be done reasonably easy, you know... :-/
> 
> If CONFIG_IP_PNP is going to go away, what is the proposed mechanism for 
> netboot devices to determine the proper source address to use when 
> searching for a rootfs to use?

My quip was mostly that it could replaced with the existing klibc 
implementation, which runs in userspace.

The other option, of course, is the distribution-specific initramfs route.

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