linux-kernel - Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]

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:	Thu, 31 Aug 2006 01:58:11 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Adrian Bunk <bunk@...sta.de>
cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	David Howells <dhowells@...hat.com>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer
 [try #2]

Hi,

On Thu, 31 Aug 2006, Adrian Bunk wrote:

> > > When doing anything kconfig related, you must always remember that the 
> > > vast majority of kconfig users are not kernel hackers.
> > 
> > What does that mean, that only kernel hackers can read?
> 
> no. But sending users from one menu to another for first manually 
> selecting this or that option is less easy for the user than the usage 
> of select.

How often does he have to do that? Is it really worth it fucking with the 
kconfig system? 

bye, Roman
-
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/