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:	Sat, 15 Sep 2007 16:11:45 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Sam Ravnborg <sam@...nborg.org>,
	James Bottomley <james.bottomley@...eleye.com>,
	linux-scsi@...r.kernel.org, Jeff Garzik <jeff@...zik.org>,
	Andi Kleen <andi@...stfloor.org>,
	Folkert van Heusden <folkert@...heusden.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] SCSI: split Kconfig menu into two

Adrian Bunk wrote:
> On Sat, Sep 15, 2007 at 03:20:06PM +0200, Stefan Richter wrote:
>> It still doesn't entirely clarify whether users need sd, sr, st, and
>> whether thy need sd for the disk with root filesystem.
> 
> If you want to do it in a really perfect way, help texts aren't the 
> solution. You'll have to make the options like CONFIG_BLK_DEV_SR no 
> longer be user visible and select'ed through dummy options like e.g.:
...
> 	tristate "USB Mass Storage hard disk support"
> 	depends on USB_STORAGE
> 	select BLK_DEV_SD
...
>         tristate "USB Mass Storage CD/DVD support"
>         depends on USB_STORAGE
> 	select BLK_DEV_SR
...

Perfect is in the eye of the beholder.  You would consequently have to
add such options into all menus which contain scsi low-level providers.

Also, one more question on whether CONFIG_SCSI ought to be 'select'ed:
Where do scsi-core options like CONFIG_SCSI_CONSTANTS go?
-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ