public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Config - general Q; default vs. suggested setting.
@ 2007-11-18 23:46 Lin Walsh
  0 siblings, 0 replies; only message in thread
From: Lin Walsh @ 2007-11-18 23:46 UTC (permalink / raw)
  To: LKML

More than once in going through configs for different
machines, I've noticed "oddities".  It's not clear which
are intentional and which 'leftovers' from changes.
Specifically, when I chose a new config by making
the default config, some of the default options
are different from what is recommended in the hint
text.

I.e. the default will have the option "on", but in the
hint(config) text, it says "this does xxyz, unless you know
what you are doing, say "no" here.
(or vice-versa)....  lets see; some examples:

Automatic kernel module loading:
Default=No, Text says "if unsure, say Y"

Under I/O Schedulers,
Default = Anticipatory, but text says: "CFQ is default"

SMT(Hyperthread)
Default:Y, Text:"If unsure say N"
Default:Y, Text:"If unsure say N"

....etc, etc...several (or many?) more...

So "Which is it"...or should there be a pattern?
If comment says "if unsure say N", or "most
users should say N", then should it be a bug
if "make defconfig" sets it to "T"("Y")?

Or should defconfig follow the help text (the answer
is probably that it depends, but does that mean a bug
should be filed against each instance?) 

I would think that the help/hint text should agree with
the default config or is there some reason for this not
to be the case?


Tnx,
Lin


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-11-18 23:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-18 23:46 Config - general Q; default vs. suggested setting Lin Walsh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox