linux-kernel - Re: tighten ATA kconfig dependancies

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

Date:	Sat, 15 Jul 2006 12:56:43 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Sam Ravnborg <sam@...nborg.org>, Dave Jones <davej@...hat.com>,
	linux-ide@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: tighten ATA kconfig dependancies


> > the point is that it doesn't fall out naturally, and thus things get
> > needlessly missed.
> 
> It seems the main question is:
> Is the kernel configuration mainly designed for users or for developers?
> 
> For users, showing drivers for hardware that is not present on their 
> platform only causes confusion.

well Aunt Tilly gets confused by all hardware that is not present on her
machine; she has no idea what a platform is. By that reasoning, we
should make kconfig hide all non-present hardware.

Also I think there is no difference in confusion between showing 10 or
15 IDE chipsets. Either the user knows what he has (and then it doesn't
matter) or those 10 are too much already.


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