linux-kernel - Re: [PATCH 2.6.24] chroot= as a new kernel parameter

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080306222254.GB8862@elte.hu>
Date:	Thu, 6 Mar 2008 23:22:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Pavel Machek <pavel@....cz>,
	Pawel Plociennik <paplociennik@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.24] chroot= as a new kernel parameter

* H. Peter Anvin <hpa@...or.com> wrote:

>> i really find it so disheartening at times that people fight trivial 
>> usability additions tooth and nail in a _9 million lines of code_ 
>> kernel with a ... "bloat" argument.
>
> Because they come in one at a time, in a completely disorganized 
> fashion (which you yourself complain on further down.)

yeah. I've got a CONFIG_BOOTPARAM patch already, which turns a lot of 
boot parameters into .config options. (this is one of our conceptual 
holes: for many boot parameters there's no matching .config)

another thing is that i think all parameters should have all their forms 
active: so if there's "noacpi", then "acpi=0/1", "acpi=off/on" should 
work as well.

furthermore, usability shortcuts for common combinations would be useful 
too. Like "serialdebug" could be used as a shortcut for 
"earlyprintk=ttyS0,115200 console=ttyS0,115200 console=vga debug". 
Things like that would be really cool.

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