All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: vojtech@suse.cz, jgarzik@pobox.com, josh@stack.nl,
	linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 20:19:19 +0000	[thread overview]
Message-ID: <0e23310182003b2DTVMAIL11@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 145 bytes --]

Then perhaps the internal speaker could be moved...

Regards, Dean.

On 	Sun, 3 Nov 2002 20:07:05 +0100 	Vojtech Pavlik <vojtech@suse.cz> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 2987 bytes --]

From: Vojtech Pavlik <vojtech@suse.cz>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jos Hulzink <josh@stack.nl>, linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 20:07:05 +0100
Message-ID: <20021103200704.A8377@ucw.cz>

On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik wrote:
> Jos Hulzink wrote:
> 
> >It took me about an hour to find out why my keyboard didn't work in 2.5.45. 
> >Well... after all it seemed that I need to enable 4 ! options inside the 
> >input configuration, just to get my default, nothing special PS/2 keyboard up 
> >and running. Oh, and I didn't even have my not so fancy boring default PS/2 
> >mouse configured then. Guys, being able to configure everything is nice, but 
> >with the 2.5 kernel, things are definitely getting out of control IMHO.
> >  
> >
> 
> This is potentially becoming a FAQ...  I ran into this too, as did 
> several people in the office.  People who compile custom kernels seem to 
> run into this when they first jump into 2.5.x.  AT Keyboard support is 
> definitely buried :/
> 
> 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.

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2002-11-03 20:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 20:19 Hell.Surfers [this message]
  -- strict thread matches above, loose matches on Subject: below --
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:25         ` 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
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

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=0e23310182003b2DTVMAIL11@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --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 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.