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:	Tue, 29 Aug 2006 16:13:33 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux-kernel@...r.kernel.org
CC:	Christoph Hellwig <hch@...radead.org>,
	David Howells <dhowells@...hat.com>,
	linux-fsdevel@...r.kernel.org, zippel@...ux-m68k.org
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer
 [try #2]

I wrote:
> If SCSI is set to "N", then any menu items which depend on SCSI are not 
> visible anymore.
[...]
> If "select" cannot be fixed or is not en vogue for any other reason, the 
> configuration tools need to be improved otherwise, so that users are 
> guided to options like USB_STORAGE and IEEE1394_SBP2 when SCSI or other 
> "foreign" options were disabled.

An easy but crude fix would be to add an according hint at the help text 
of the immediately superordinate config option. E.g. at IEEE1394: "Also 
enable SCSI support to be able to switch on SBP-2 support (IEEE 1394 
protocol e.g. for storage devices)." But this is extremely ugly /1./ 
because it would litter help texts of generic options with redundant 
information about specific options and /2./ because it requires users to 
find and read help texts in order to convince the configurator to make 
options visible.
-- 
Stefan Richter
-=====-=-==- =--- ===-=
http://arcgraph.de/sr/
-
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/