From: Andries Brouwer <aebr@win.tue.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Jeff Garzik <jgarzik@pobox.com>, Jos Hulzink <josh@stack.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 22:58:33 +0100 [thread overview]
Message-ID: <20021103215833.GA946@win.tue.nl> (raw)
In-Reply-To: <20021103200704.A8377@ucw.cz>
On Sun, Nov 03, 2002 at 08:07:05PM +0100, Vojtech Pavlik wrote:
> > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > subsystem maintainer), just a request that it becomes easier and more
> > obvious how to configure the keyboard and mouse that is found on > 90%
> > of all Linux users computers [IMO]...
>
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
Last month or so I suggested adding a hint for Appletalk, and I see
that it is there now:
config LLC
tristate "ANSI/IEEE 802.2 Data link layer protocol (IPX, Appletalk)"
Such parenthetical remarks will no doubt help a little.
You might try
--- Kconfig~ Thu Oct 31 14:15:06 2002
+++ Kconfig Sun Nov 3 22:51:45 2002
@@ -5,7 +5,7 @@
menu "Input device support"
config INPUT
- tristate
+ tristate "Input devices (needed for mouse, keyboard, ...)"
default y
---help---
Say Y here if you have any input device (mouse, keyboard, tablet,
and
--- Kconfig~ Thu Oct 31 14:15:06 2002
+++ Kconfig Sun Nov 3 22:54:28 2002
@@ -2,7 +2,7 @@
# Input core configuration
#
config SERIO
- tristate "Serial i/o support"
+ tristate "Serial i/o support (needed for keyboard and mouse)"
---help---
Say Yes here if you have any input device that uses serial I/O to
communicate with the system. This includes the
(and maybe also sth under keyboard, to tell people that what they have
is called an AT keyboard).
Andries
next prev parent reply other threads:[~2002-11-03 21:52 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
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 [this message]
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=20021103215833.GA946@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=jgarzik@pobox.com \
--cc=josh@stack.nl \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox