From: Nick Andrew <nick@nick-andrew.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Francis Moreau <francis.moro@gmail.com>,
"Renato S. Yamane" <yamane@diamondcut.com.br>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: About git-bisect (defconfigs)
Date: Thu, 4 Dec 2008 11:14:52 +1100 [thread overview]
Message-ID: <20081204001452.GH11807@mail.local.tull.net> (raw)
In-Reply-To: <4936C6FB.4020201@oracle.com>
On Wed, Dec 03, 2008 at 09:50:51AM -0800, Randy Dunlap wrote:
> 2. There are several security-related config items that default to =y but the
> kconfig help says: If unsure, say N here. Like:
>
>
> CONFIG_NETLABEL=y
> CONFIG_NETWORK_SECMARK=y
> CONFIG_KEYS=y
> CONFIG_SECURITY=y
> CONFIG_SECURITY_NETWORK=y
> CONFIG_SECURITY_SELINUX=y
>
> Maybe I just don't understand the current meaning/usage of defconfig. eh?
A consistent approach to the Kconfig hints would help. To me,
"If unsure, say N" implies that turning off the feature won't break
the kernel nor be anything particularly important. The Kconfig hints
should follow the defaults (or else why default to 'y'?) for common
architectures.
Perhaps menuconfig can generate the "If unsure" message itself from
the architecture defaults? That will ensure consistency.
Nick.
prev parent reply other threads:[~2008-12-04 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bEuTZ-3Ya-5@gated-at.bofh.it>
[not found] ` <bECot-57C-1@gated-at.bofh.it>
[not found] ` <bEFPF-XO-15@gated-at.bofh.it>
[not found] ` <bEFPG-XO-19@gated-at.bofh.it>
[not found] ` <bEG8P-1xl-15@gated-at.bofh.it>
[not found] ` <bEGiz-1Hw-11@gated-at.bofh.it>
[not found] ` <bEGLI-2aS-31@gated-at.bofh.it>
[not found] ` <bEGVc-2Bk-11@gated-at.bofh.it>
[not found] ` <m2r64q6y8e.fsf@gmail.com>
[not found] ` <493681B7.20101@diamondcut.com.br>
[not found] ` <38b2ab8a0812030924g5391fdbdy15c472a51ab24aef@mail.gmail.com>
2008-12-03 17:50 ` About git-bisect (defconfigs) Randy Dunlap
2008-12-04 0:14 ` Nick Andrew [this message]
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=20081204001452.GH11807@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=yamane@diamondcut.com.br \
/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).