linux-kernel - Re: [patch 01/10] e1000e: make E1000E default to the same kconfig setting as E1000

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]

Message-ID: <20071215000234.GB5403@stusta.de>
Date:	Sat, 15 Dec 2007 01:02:34 +0100
From:	Adrian Bunk <bunk@...nel.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	randy.dunlap@...cle.com, auke-jan.h.kok@...el.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch 01/10] e1000e: make E1000E default to the same kconfig
	setting as E1000

On Fri, Dec 14, 2007 at 06:17:55PM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
>> On Fri, Dec 14, 2007 at 03:39:26PM -0500, Jeff Garzik wrote:
>>> akpm@...ux-foundation.org wrote:
>>>> From: Randy Dunlap <randy.dunlap@...cle.com>
>>> ...
>>> So I think the breakage that occurs is mitigated by two factors:
>>> 1) kernel hackers that do their own configs are expected to be able to 
>>> figure this stuff.
>>> 2) kernel builders (read: distros, mainly) are expected to have put 
>>> thought into the Kconfig selection and driver migration strategies.
>>> ...
>>> I would prefer simply to communicate to kernel experts and builders about 
>>> a Kconfig issue that could potentially their booting/networking...  
>>> because this patch is only needed if the kernel experts do not already 
>>> know about a necessary config update.
>>
>> You miss the vast majority of kconfig users:
>>
>> 3) system administrators etc. who for different reasons compile their own 
>> kernels but neither are nor want to be kernel developers
>>
>> There's a reason why e.g. LPI requires you to be able to compile your own 
>> kernel even for getting a "Junior Level Linux Professional" certificate.
>
> Great!
>
>
>> Or that one of the authors of "Linux Device drivers" has written a book 
>> covering only how to build and run your own kernel.
>
> Nonetheless, it will always be true that configuring your own kernel 
> requires knowledge of the options you are setting.

We are not talking about Aunt Tillie, "system administrator" is the use 
case that might cover this (quite diverse) group of users best.

We can expect kconfig users to know what filesystems their data is on 
and to have some knowledge of their hardware, but every other knowledge 
we must give through kconfig.

> 	Jeff

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

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