linux-kernel - Re: Fix sudden warps in mousedev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Mar 2007 12:19:10 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Chuck Ebbert" <cebbert@...hat.com>
Cc:	"Pete Zaitcev" <zaitcev@...hat.com>, linux-kernel@...r.kernel.org,
	linux-input@...ey.karlin.mff.cuni.cz,
	"Peter Osterlund" <petero2@...ia.com>
Subject: Re: Fix sudden warps in mousedev

On 3/27/07, Chuck Ebbert <cebbert@...hat.com> wrote:
> Dmitry Torokhov wrote:
> >>
> >> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
> >> mouse1 became mouse2 for many people?
> >
> > Input devices are not guaranteed to be stable.
> >
>
> So people with z-axis mice need to redo their X config for each
> kernel release when the device numbers change? Or should they
> be using some other configuration?
>
> People using this now have X crashes on kernel upgrade because
> event1 became event2:
>
>        Driver      "evdev"
>        Option      "Device" "/dev/input/event1"
>

I'd recommend matching on "phys" or individual capabilities bits
instead of device node. See "man evdev".

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