linux-kernel - Re: [PATCH 00/26] Dynamic kernel command-line

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]

Date:	Mon, 4 Sep 2006 08:05:44 +0300
From:	"Alon Bar-Lev" <alon.barlev@...il.com>
To:	"Paul Mackerras" <paulus@...ba.org>
Cc:	"Andi Kleen" <ak@...e.de>, "Matt Domsch" <Matt_Domsch@...l.com>,
	"Andrew Morton" <akpm@...l.org>, linux-kernel@...r.kernel.org,
	johninsd@....rr.com, davej@...emonkey.org.uk, Riley@...liams.name,
	trini@...nel.crashing.org, davem@...emloft.net, ecd@...inaid.de,
	jj@...site.ms.mff.cuni.cz, anton@...ba.org, wli@...omorphy.com,
	lethal@...ux-sh.org, rc@....org.uk, spyro@....com, rth@...ddle.net,
	avr32@...el.com, hskinnemoen@...el.com, starvik@...s.com,
	ralf@...ux-mips.org, matthew@....cx, grundler@...isc-linux.org,
	geert@...ux-m68k.org, zippel@...ux-m68k.org,
	schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
	uclinux-v850@....nec.co.jp, chris@...kel.net
Subject: Re: [PATCH 00/26] Dynamic kernel command-line

On 9/4/06, Paul Mackerras <paulus@...ba.org> wrote:
> Alon Bar-Lev writes:
>
> > Current implementation stores a static command-line
> > buffer allocated to COMMAND_LINE_SIZE size. Most
> > architectures stores two copies of this buffer, one
> > for future reference and one for parameter parsing.
>
> Under what circumstances do we actually need a command line of more
> than 256 bytes?

Sure!
With static modules options, splash support, disk encryption, suspend,
local initrd settings we need much more than 256 bytes...

> It seems to me that if 256 bytes isn't enough, we should take a deep
> breath, step back, and think about whether there might be a better way
> to pass whatever information it is that's using up so much of the
> command line.

But the command line is a wonderful tool... It allows you to compile
the same kernel/initramfs and install it on different machines,
modifying only the boot loader configuration file. It also allows
several boot profiles at boot loader level, without the need to
replaces files or have complex initrd...
 So it worth modifying current implementation.

Best Regards,
Alon Bar-Lev.

-- 
VGER BF report: H 0
-
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/