public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh@stack.nl>
To: Vojtech Pavlik <vojtech@suse.cz>, Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 22:39:10 +0100	[thread overview]
Message-ID: <200211032239.10843.josh@stack.nl> (raw)
In-Reply-To: <20021103200704.A8377@ucw.cz>

On Sunday 03 November 2002 20:07, Vojtech Pavlik wrote:
> On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik 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.

Something I have been thinking about for a while is a quick-config option 
(that sets some defaults that hold for 90% of the systems), or an expert mode 
that shows extra options. Though I understand that this is hard to do, and 
much hardware differs, I think it can be done for some basics like keyboard, 
mouse, USB and stuff.

Yes, this will cause your kernel to be bigger than optimal, for some drivers 
will be compiled in that are not used on your system. But if you want you can 
optimize things away after clicking <set defaults for standard IBM PC>.

If this idea is not blown away immediately, I'm willing to work this idea out 
a little, though I can understand that people call me an idiot...

Jos



  parent reply	other threads:[~2002-11-03 19:34 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 [this message]
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=200211032239.10843.josh@stack.nl \
    --to=josh@stack.nl \
    --cc=jgarzik@pobox.com \
    --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