From: Vojtech Pavlik <vojtech@suse.cz>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Andrew Morton <akpm@osdl.org>,
Dmitry Torokhov <dtor_core@ameritech.net>,
linux-kernel@vger.kernel.org
Subject: Re: Fw: Re: keyboard problem with 2.6.6
Date: Sat, 29 May 2004 16:18:33 +0200 [thread overview]
Message-ID: <20040529141833.GA14849@ucw.cz> (raw)
In-Reply-To: <20040529140736.GD5175@pclin040.win.tue.nl>
On Sat, May 29, 2004 at 04:07:36PM +0200, Andries Brouwer wrote:
> On Sat, May 29, 2004 at 09:09:53AM +0200, Vojtech Pavlik wrote:
>
> > One more thought: The emulated PS/2 mouse so many people are complaining
> > about is there only because applications like X cannot use the native
> > event interface. It was intended to be removed after that support is
> > added, but with X development being as slow as it is, it didn't ever
> > happen.
>
> A mistake.
Well, yes. It's just 99% compatible, and it wasn't removed yet. But I
still hope it eventually will.
> You add new functionality. That is good. At the same time you want
> to force people to use this new stuff by throwing out the old. Bad.
>
> It is almost impossible to remove features from the kernel.
I had hoped with so few programs using it (basically only X), it
shouldn't be so impossible.
> People have a great variety of user space setups, and can have
> lots of reasons why it is undesirable or impossible to change
> their software, while a new kernel may be required to support
> new hardware or for security reasons.
>
> One should always (i) go in a long series of tiny steps,
> (ii) attempt to be 100% backwards compatible.
> Obsoleting old stuff is done over a period of more than
> five years, if at all.
>
> Andries
>
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2004-05-29 14:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040528154307.142b7abf.akpm@osdl.org>
2004-05-29 7:09 ` Fw: Re: keyboard problem with 2.6.6 Vojtech Pavlik
2004-05-29 13:14 ` Giuseppe Bilotta
2004-05-29 13:37 ` Vojtech Pavlik
2004-05-29 15:12 ` Giuseppe Bilotta
2004-05-29 15:44 ` Vojtech Pavlik
2004-05-29 17:18 ` Dmitry Torokhov
2004-05-29 18:23 ` Vojtech Pavlik
2004-05-30 10:20 ` Giuseppe Bilotta
2004-05-30 11:43 ` Vojtech Pavlik
2004-05-30 12:38 ` Giuseppe Bilotta
2004-05-30 12:59 ` Vojtech Pavlik
2004-05-30 16:08 ` Giuseppe Bilotta
2004-05-30 20:31 ` Vojtech Pavlik
2004-05-30 20:51 ` Giuseppe Bilotta
2004-05-30 21:28 ` Vojtech Pavlik
2004-05-31 12:43 ` Giuseppe Bilotta
2004-05-30 23:21 ` keyboard: kernel and X Andries Brouwer
2004-05-31 12:43 ` Giuseppe Bilotta
2004-06-01 11:22 ` Fw: Re: keyboard problem with 2.6.6 Vojtech Pavlik
2004-05-29 22:40 ` Dmitry Torokhov
2004-05-29 14:07 ` Andries Brouwer
2004-05-29 14:18 ` Vojtech Pavlik [this message]
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=20040529141833.GA14849@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
/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