linux-kernel - Re: [PATCH] x86_64, i386: Add command line length to boot protocol

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: <20070312233946.GE21835@redhat.com>
Date:	Mon, 12 Mar 2007 19:39:46 -0400
From:	Dave Jones <davej@...hat.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, alon.barlev@...il.com,
	ak@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64, i386: Add command line length to boot protocol

On Tue, Mar 13, 2007 at 12:12:20AM +0100, Pavel Machek wrote:

 > > 65535 characters? Are you for real?
 > > Stop and think about just how big that is. If you have to create
 > > a boot command line that long, you have serious, serious issues.
 > 
 > Well, it is about the same size as my .config...

So? That has *nothing* to do with the boot command line

 > I agree we are unlikely to hit it any time soon... I could imagine
 > some (ab)uses, like fixed_acpi_bios=<lots of hex digits>, but those
 > are ugly.

That's beyond ugly, and rapidly heading towards 'loony'.

 > I could also imagine some uses where entire embedded machine
 > is described at kernel commandline.

There are far better ways to get configuration into the kernel
than the boot command line.

Anyways, I'm tired of arguing for the sake of arguing.
I really could care less.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/