From: William Lee Irwin III <wli@holomorphy.com>
To: Miles Bader <miles@gnu.org>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
Jeff Garzik <jgarzik@pobox.com>, Jos Hulzink <josh@stack.nl>
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 18:46:31 -0800 [thread overview]
Message-ID: <20021104024631.GU23425@holomorphy.com> (raw)
In-Reply-To: <87y98a6omx.fsf@tc-1-100.kawasaki.gol.ne.jp>
On Mon, Nov 04, 2002 at 11:43:18AM +0900, Miles Bader wrote:
> Keep in mind that All the World's Not a PC. No doubt those options are
> enabled on the majority of kernels, by number, but linux supports many,
> many types of systems, and I'll bet on fair number of them, it doesn't
> make much sense to enable psaux mouse support!
> So ... instead of saying `default y' for these options, how about saying
> `default IM_ON_A_PC' where IM_ON_A_PC is defined somehow. How, I don't
> know; it could be a separate config question in a very obvious place,
> perhaps itself having `default X86'.
> Perhaps this should really be two flags, one IM_ON_A_PC meaning `typical
> i386 pc with legacy devices', and the other, more general, being
> something like IM_ON_A_WORKSTATION. Then wierd things like psaux would
> say `default IM_ON_A_PC', but more general things like keyboards would
> say `default IM_ON_A_WORKSTATION'.
> [Yeah, those names are sucky, I know...]
> Thanks,
> -Miles
How about a PC subarch and turning them on by default for it?
Bill
next prev parent reply other threads:[~2002-11-04 2:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 17:09 Petition against kernel configuration options madness Jos Hulzink
2002-11-03 16:05 ` Tomas Szepe
2002-11-03 18:20 ` Jos Hulzink
2002-11-03 17:52 ` Jeff Garzik
2002-11-03 19:07 ` Vojtech Pavlik
2002-11-03 19:37 ` Petr Baudis
2002-11-03 20:13 ` Vojtech Pavlik
2002-11-03 22:20 ` Petr Baudis
2002-11-03 22:32 ` [PATCH] Sane defaults for the input layer configuration Petr Baudis
2002-11-03 22:25 ` Petition against kernel configuration options madness Jos Hulzink
2002-11-04 1:40 ` Randy.Dunlap
2002-11-04 2:43 ` Miles Bader
2002-11-04 2:46 ` William Lee Irwin III [this message]
2002-11-03 20:38 ` Arador
2002-11-03 20:40 ` Nicholas Wourms
2002-11-03 21:39 ` Jos Hulzink
2002-11-03 22:04 ` Nick LeRoy
2002-11-03 21:58 ` Andries Brouwer
2002-11-03 21:59 ` Dave Jones
2002-11-03 22:18 ` Brad Hards
2002-11-04 0:06 ` Werner Almesberger
2002-11-04 13:05 ` Mr. James W. Laferriere
2002-11-03 20:38 ` Nicholas Wourms
2002-11-03 20:43 ` Arador
2002-11-03 21:11 ` Flavio Stanchina
2002-11-03 21:22 ` Nicholas Wourms
2002-11-03 21:48 ` Flavio Stanchina
2002-11-03 22:00 ` Matthias Schniedermeyer
2002-11-04 0:18 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 20:19 Hell.Surfers
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=20021104024631.GU23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=jgarzik@pobox.com \
--cc=josh@stack.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.