From: Robert Love <rml@tech9.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Adrian Bunk <bunk@fs.tum.de>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: observations on 2.5 config screens
Date: 08 Jan 2003 10:53:15 -0500 [thread overview]
Message-ID: <1042041195.694.2734.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.3.96.1030108093021.21759B-100000@gatekeeper.tmr.com>
On Wed, 2003-01-08 at 09:32, Bill Davidsen wrote:
> Someone else suggested putting all the low level options like preempt,
> smp, and the stuff in kernel-hacking into a single menu, with a better
> name.
I do not think I like this. SMP, kernel preemption, and high memory
support are the three most fundamental choices one makes during
configuration.
They should be out in the open, in the beginning, in a well-labeled
category. They only issue I see is "processor options" should be
renamed "core options" or whatever. But that is trivial.
Robert Love
next prev parent reply other threads:[~2003-01-08 16:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 19:55 observations on 2.5 config screens Robert P. J. Day
2003-01-01 20:07 ` Tomas Szepe
2003-01-01 20:15 ` Robert P. J. Day
2003-01-01 20:26 ` John Bradford
2003-01-02 1:55 ` Randy.Dunlap
2003-01-02 2:32 ` Robert P. J. Day
2003-01-02 4:10 ` Randy.Dunlap
2003-01-02 2:54 ` Tomas Szepe
2003-01-07 23:07 ` [2.5 patch] MODULE_FORCE_UNLOAD must depend on MODULE_UNLOAD Adrian Bunk
2003-01-08 12:05 ` Rusty Russell
2003-01-07 23:30 ` observations on 2.5 config screens Adrian Bunk
2003-01-07 23:42 ` Robert Love
2003-01-08 0:14 ` Russell King
2003-01-08 14:32 ` Bill Davidsen
2003-01-08 15:53 ` Robert Love [this message]
2003-01-08 18:36 ` Bill Davidsen
2003-01-08 19:50 ` Dave Jones
2003-01-08 22:49 ` Bill Davidsen
2003-01-09 12:50 ` Dave Jones
2003-01-09 16:12 ` Bill Davidsen
2003-01-09 13:38 ` Ruslan U. Zakirov
[not found] <Pine.LNX.4.44.0301011435300.27623-100000@dell.qualified-at.bofh.it>
2003-01-02 23:50 ` Bill Davidsen
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=1042041195.694.2734.camel@phantasy \
--to=rml@tech9.net \
--cc=bunk@fs.tum.de \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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