public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4: disabling SCSI support not possible
Date: Mon, 05 Apr 2004 18:17:14 -0400	[thread overview]
Message-ID: <c4slos$6tq$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040402181630.B12306@flint.arm.linux.org.uk>

Russell King wrote:
> On Fri, Apr 02, 2004 at 08:59:41AM -0800, Greg KH wrote:
> 
>>No, this is the way it used to be, and it caused all kinds of problems
>>in the past.  It was switched to use 'select' on purpose, and should
>>stay that way.
> 
> 
> It's causing problems today by preventing people from being able to
> de-select SCSI for no obvious reason.
> 
> It is far less intuitive to know you have to turn off USB_STORAGE
> before you can turn off SCSI than to know that you have to turn on
> SCSI before you can turn on USB_STORAGE.

Intuitive isn't the issue, if you can't figure out why you can't turn 
off SCSI, you leave it on, which you need to make USB storage work. If 
you're trying to make a small kernel you presumably would have turned 
off USB if you didn't want it. The other way, if you can turn on USB w/o 
SCSI, it won't work, and people thing Linux is broken.

The issue is that what we have works but it's not obvious why, vs. 
doesn't work and also isn't obvious why. Thank you, work by default is 
better.
> 
> If you wish to keep it this way, could we either have:
> 
> (a) a note in the SCSI help text to say that the option is forced
>     on by USB_STORAGE, so people know what to turn off.

Chances are that most people wouldn't have USB on if they didn't want 
it, but there's no downside to doing this.
> 
> or
> 
> (b) have kconfig tell you why you can't turn off the option.

I thought that was what (a) did.
> 
> Silently preventing options being turned off with no obvious reason
> is a pretty major misfeature.

Compared to enabling USB storage with no hope of having it work? Adding 
user info is desirable, but making it easy, or even possible, to build a 
  non-working config is a lot more of a problem. You haven't compiled on 
a slow machine lately, forcing config combinations which work is a 
benefit of kconfig.

If you want it broken you have to edit the config code. That's a good thing.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-04-05 22:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 13:09 2.6.4: disabling SCSI support not possible Olaf Zaplinski
2004-04-02 13:18 ` Grzegorz Kulewski
2004-04-02 13:21 ` Sean Neakums
2004-04-02 13:42   ` Russell King
2004-04-02 14:03     ` Marc-Christian Petersen
2004-04-02 16:59     ` Greg KH
2004-04-02 17:16       ` Russell King
2004-04-02 17:56         ` Kevin P. Fleming
2004-04-02 18:14         ` Greg KH
2004-04-05 22:17         ` Bill Davidsen [this message]
2004-04-06  8:42           ` Russell King
2004-04-06 10:46             ` Marc-Christian Petersen
2004-04-06 11:03               ` Marc-Christian Petersen
2004-04-02 19:29     ` Ricky Beam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='c4slos$6tq$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox