From: Adrian Bunk <bunk@kernel.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jeff Garzik <jeff@garzik.org>, Andi Kleen <andi@firstfloor.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Folkert van Heusden <folkert@vanheusden.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: sata & scsi suggestion for make menuconfig
Date: Fri, 14 Sep 2007 18:16:19 +0200 [thread overview]
Message-ID: <20070914161619.GM3563@stusta.de> (raw)
In-Reply-To: <46EAAAC1.3050409@s5r6.in-berlin.de>
On Fri, Sep 14, 2007 at 05:37:37PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
> >> The patch which is discussed here is specifically targeted towards users
> >> who are convinced that they can migrate to different drivers without
> >> reading Kconfig help texts.
> >
> > Nothing about the patch is only about migration.
> >
> > The same applies if you configure a kernel from scratch.
> >
> > Do "make menuconfig" with the .config you are normally using, count the
> > number of options that are visible, and ask yourself whether we can
> > really expect users to read the help texts for every single option shown.
> >
> > People mostly read help texts for options where they don't understand
> > what this option is about - and "Serial ATA" therefore is an option that
> > is likely to get enabled without the user looking at the help text.
>
> If you create .config from scratch, then you can get away without
> reading help texts if you have a target with minimal hardware and
> protocols requirements and you know all the subsystems involved.
>
> In all other cases, you theoretically need to read all help texts (minus
> the ones that don't appear because you deselect entire subsystems). In
> practice, this takes too much time, hence you take an existing .config
> (yours or somebody else's) and go from there.
Kconfig let's you start with the defconfig when doing "make menuconfig"
without any .config present, so in practice users start from the
defconfig and then go through all menus at once enabling and disabling
options to adapt the configurations to their needs.
Or they start from the "includes everything" .config of their
distribution and remove everything they don't need.
> Whenever one enables an option for the first time, it would IMO be
> foolish to ignore its help text.
Then the number of non-foolish users is quite near to 0...
If you expect people to read several hundreds or thousands of help texts
only for configuring a kernel then you are expecting something that is
simply not realistic.
It is intuitive for a user to enable the "Serial ATA" menu and he might
not expect to have to read the help text when he has SATA drivers, while
having to enable anything in the "SCSI device support" menu is highly
unintuitively when the user does not have SCSI hardware.
> Stefan Richter
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-09-14 16:16 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 12:48 sata & scsi suggestion for make menuconfig Folkert van Heusden
2007-09-07 14:40 ` Jan Engelhardt
2007-09-07 14:58 ` Folkert van Heusden
2007-09-07 19:38 ` Krzysztof Halasa
2007-09-07 23:02 ` Jan Engelhardt
2007-09-08 7:27 ` Jan Engelhardt
2007-09-07 15:35 ` Randy Dunlap
2007-09-07 15:59 ` Folkert van Heusden
2007-09-07 16:21 ` Stefan Richter
2007-09-07 23:05 ` Folkert van Heusden
2007-09-08 7:05 ` Stefan Richter
2007-09-08 7:29 ` Jan Engelhardt
2007-09-08 7:56 ` Stefan Richter
2007-09-08 16:31 ` Randy Dunlap
2007-09-08 16:44 ` Stefan Richter
2007-09-08 16:48 ` Randy Dunlap
2007-09-08 19:45 ` Stefan Richter
2007-09-08 8:43 ` Sam Ravnborg
2007-09-13 8:50 ` Helge Hafting
2007-09-14 16:42 ` Goswin von Brederlow
2007-09-14 18:44 ` Stefan Richter
2007-09-08 16:07 ` Andi Kleen
2007-09-08 16:50 ` Randy Dunlap
2007-09-08 16:53 ` Matthew Wilcox
2007-09-08 18:13 ` Andi Kleen
2007-09-08 18:30 ` Stefan Richter
2007-09-08 19:14 ` Andi Kleen
2007-09-08 19:32 ` Stefan Richter
2007-09-09 21:00 ` James Bottomley
2007-09-09 21:03 ` Andi Kleen
2007-09-09 21:11 ` Jeff Garzik
2007-09-09 21:22 ` Andi Kleen
2007-09-09 21:39 ` James Bottomley
2007-09-10 6:38 ` Stefan Richter
2007-09-10 12:43 ` Rene Herman
2007-09-11 20:16 ` Bauke Jan Douma
2007-09-12 22:46 ` Adrian Bunk
2007-09-14 14:54 ` Stefan Richter
2007-09-14 15:15 ` Adrian Bunk
2007-09-14 15:37 ` Stefan Richter
2007-09-14 16:01 ` [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage Stefan Richter
2007-09-14 16:29 ` Jeff Garzik
2007-09-14 18:02 ` [RFC PATCH] SCSI: split Kconfig menu into two Stefan Richter
2007-09-14 18:04 ` [PATCH] SCSI: trailing whitespace in Kconfig Stefan Richter
2007-09-14 19:00 ` [RFC PATCH] SCSI: split Kconfig menu into two Sam Ravnborg
2007-09-14 19:06 ` Adrian Bunk
2007-09-14 20:01 ` Stefan Richter
2007-09-15 11:40 ` Adrian Bunk
2007-09-15 12:24 ` Stefan Richter
2007-09-15 12:50 ` Adrian Bunk
2007-09-15 13:20 ` Stefan Richter
2007-09-15 13:53 ` Adrian Bunk
2007-09-15 14:11 ` Stefan Richter
2007-09-15 14:43 ` Adrian Bunk
2007-09-15 15:27 ` Stefan Richter
2007-09-15 15:44 ` Jeff Garzik
2007-09-15 16:23 ` Adrian Bunk
2007-09-15 16:52 ` Bartlomiej Zolnierkiewicz
2007-09-15 19:17 ` Jeff Garzik
2007-09-15 20:54 ` Bartlomiej Zolnierkiewicz
2007-09-16 20:12 ` Greg KH
2007-09-15 16:42 ` Adrian Bunk
2007-09-17 11:29 ` Maciej W. Rozycki
2007-09-17 14:46 ` Stefan Richter
2007-09-14 20:20 ` Stefan Richter
2007-09-14 21:22 ` [PATCH update] " Stefan Richter
2007-09-14 18:54 ` [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage Lennart Sorensen
2007-09-14 20:14 ` Stefan Richter
2007-09-14 20:21 ` Lennart Sorensen
2007-09-14 21:06 ` Stefan Richter
2007-09-14 21:11 ` Lennart Sorensen
2007-09-14 21:14 ` [PATCH update] " Stefan Richter
2007-09-14 22:02 ` FUJITA Tomonori
2007-09-15 6:16 ` Stefan Richter
2007-09-15 10:52 ` FUJITA Tomonori
2007-09-15 12:30 ` Stefan Richter
2007-09-15 12:53 ` FUJITA Tomonori
2007-09-15 12:59 ` Adrian Bunk
2007-09-15 13:19 ` Stefan Richter
2007-09-14 16:16 ` Adrian Bunk [this message]
2007-09-14 16:50 ` sata & scsi suggestion for make menuconfig Stefan Richter
2007-09-15 8:04 ` Paul Rolland
2007-09-15 8:25 ` Stefan Richter
2007-09-15 13:00 ` Paul Rolland
2007-09-15 15:50 ` x86_64 usability bug: Kconfig prompt without help text (was Re: sata & scsi suggestion for make menuconfig) Stefan Richter
2007-09-15 16:21 ` Andi Kleen
2007-09-15 17:13 ` [PATCH] x86_64: configure HPET_EMULATE_RTC automatically Stefan Richter
2007-09-15 18:23 ` sata & scsi suggestion for make menuconfig david
-- strict thread matches above, loose matches on Subject: below --
2007-09-08 3:52 Al Boldi
2007-09-08 13:47 ` Alan Cox
2007-09-08 14:03 ` Al Boldi
2007-09-08 16:08 ` Jan Engelhardt
2007-09-09 4:11 ` Al Boldi
[not found] <90ZEn-1YU-3@gated-at.bofh.it>
[not found] ` <918Rh-7Or-5@gated-at.bofh.it>
[not found] ` <919aD-8ua-7@gated-at.bofh.it>
2007-09-08 16:52 ` Bodo Eggert
2007-09-08 18:22 ` Stefan Richter
2007-09-08 18:54 ` Randy Dunlap
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=20070914161619.GM3563@stusta.de \
--to=bunk@kernel.org \
--cc=James.Bottomley@SteelEye.com \
--cc=andi@firstfloor.org \
--cc=folkert@vanheusden.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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