linux-kernel - Re: Linux 2.6.22-rc1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 May 2007 12:43:47 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Satyam Sharma <satyam.sharma@...il.com>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Stefan Richter <stefanr@...6.in-berlin.de>
Subject: Re: Linux 2.6.22-rc1

Hi,

Satyam Sharma schrieb:

>>   * Since Jens Axboe's stance ["default y idiocy"] is to have
>>     these menus disabled by default, people should most likely
>>     enable them first before they will be able to enter them.
> 
> I do agree that anything non-essential (even if it's just a presentation
> menu that doesn't affect builds) must be default n.

It's tricky for "make oldconfig" when introducing a new "menuconfig"
around some previously existing "config"s, because just accepting
the default for the new option then causes previously selected
ones to be silently dropped. But I don't know a perfect solution
for that. Perhaps we'll just have to live with it. Or perhaps a
warning message along the line of "deselecting option xxx" would
be in order.

> IMHO, the real problem with "default y" menuconfig's, is that they
> cause unpleasant surprises to those folks that use the text-based
> "make oldconfig". They get confronted with choices that they never
> bothered about (or even knew existed) previously, and have no
> idea how to answer them -- same problem faced by Tilman, when
> he used oldconfig.

It's actually the other way around, all those options now tucked
underneath the menuconfig were previously directly visible, so
selecting "y" (either explicitly or by default) makes everything
work as before while "n" very conveniently skips them all.
It's really quite nice if you know how it works. The only thing
that's missing is instructions for those seeing it for the first
time.

> IMHO, those using "oldconfig" are often looking towards doing
> things quickly ... doesn't help them if they have default y menu's
> that they need to "?" upon then to see what they're really about.

Well, yes and no. I am of course trying to get through the new
options as quickly as possible. But if I hit an option I don't
understand then typing "?" is the quickest way to sort it out,
so it's doubly annoying if that yields nothing.

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)