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]

Message-ID: <20060901161920.GB32440@wohnheim.fh-wedel.de>
Date:	Fri, 1 Sep 2006 18:19:20 +0200
From:	Jörn Engel <joern@...nheim.fh-wedel.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Adrian Bunk <bunk@...sta.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]

On Fri, 1 September 2006 17:31:51 +0200, Stefan Richter wrote:
> 
> Yes and no. In the latter case, they have to magically know that at
> least menuconfig and xconfig can be tricked to list depending options.

True.  Marginally better than horrible then. :)

> Could be a fun project [...]

Absolutely.  Assuming that select gets removed in the process, and
concentrating on oldconfig, would it be enough to have something like
this in the .config?

# CONFIG_USB_STORAGE has unmet dependencies: CONFIG_SCSI, CONFIG_BLOCK

Now people looking for usb mass storage can find the option without
grepping through Kconfig files, but also every single driver for every
single disabled subsystem shows up.  Might be a bit too much.

Jörn

-- 
Invincibility is in oneself, vulnerability is in the opponent.
-- Sun Tzu
-
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/