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
Subject: Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
Date: Sun, 17 Jun 2007 18:38:00 -0700 [thread overview]
Message-ID: <1182130680.22999.13.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4675DFA8.6060703@gentoo.org>
> 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
next prev parent reply other threads:[~2007-06-18 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 23:40 AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h Alexander Gabert
2007-06-18 1:06 ` Arjan van de Ven
2007-06-18 1:28 ` Alexander Gabert
2007-06-18 1:38 ` Arjan van de Ven [this message]
2007-06-18 10:36 ` Alexander Gabert
2007-06-20 15:34 ` [PATCH] get_random_long() and AT_ENTROPY for auxv, kernel 2.6.21.5 Alexander Gabert
2007-06-20 15:38 ` Arjan van de Ven
2007-06-20 16:39 ` Linus Torvalds
2007-06-20 17:04 ` Eric Dumazet
2007-06-20 20:30 ` Matt Mackall
2007-06-24 17:45 ` Alexander Gabert
2007-06-25 3:45 ` Matt Mackall
2007-06-25 4:43 ` Arjan van de Ven
2007-06-25 5:12 ` Matt Mackall
2007-06-25 7:09 ` Jakub Jelinek
2007-06-25 15:02 ` Alexander Gabert
2007-06-25 15:20 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1182130680.22999.13.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=hardened@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pappy@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).