linux-kernel - Config - general Q; default vs. suggested setting.

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>] [day] [month] [year] [list]

Date:	Sun, 18 Nov 2007 15:46:44 -0800
From:	Lin Walsh <lkml@...nx.org>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Config - general Q; default vs. suggested setting.

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

-
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/