Subject: Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
From: Arjan van de Ven <arjan@infradead.org>
To: Alexander Gabert <pappy@gentoo.org>
Cc: libc-alpha@sourceware.org, linux-kernel@vger.kernel.org,
       hardened@gentoo.org
In-Reply-To: <4675DFA8.6060703@gentoo.org>
References: <4675C678.3080807@gentoo.org>
	 <1182128803.22999.9.camel@laptopd505.fenrus.org>
	 <4675DFA8.6060703@gentoo.org>
Content-Type: text/plain
Organization: Intel International BV
Date: Sun, 17 Jun 2007 18:38:00 -0700
Message-Id: <1182130680.22999.13.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1060
Lines: 24


> Hence the config option for the kernel- it's philosophy at Gentoo to 
> make choices available to users how they want their systems to behave, 
> even on the expense of added complexity and need to "understand" how 
> things work in the first place.

While I am not opposed to choice, I am opposed to having too finegrained
kernel config options. In your view, every single kernel patch would be
a config option... I much rather have config options for "important" big
changes, not for something this small. Another argument is that this
kind of userspace interface is better off being always there or never;
making this variable serves no-one.


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/