Re: 'Phys:' field for keyboards (and other input devices)

[Andreas S. <an...@sc...>]

* Vojtech Pavlik (vo...@su...) [020927 09:54]:
> > it is important to bind Keyboards to VTs to be able to start
> > Xservers on that VT. Mice (for X) can be configured in the
> > XF86Config. but it would perhaps be nice to be able to configure
> > which mouse goes with which /dev/input/mouse* device, which in
> > turn get used in the XF86Config. Do people agree on this or is
> > that unneeded featureism?
> 
> No, X should be taught to open the correct /dev/input/event* device (not
> mouse*), based on a phys (or ID or ...) entry given in XF86Config.

And that is because the /dev/input/event* is the thing of the
future and mouse* will pass away? 

But my point was really to have a way to determine/configure
which mouse would become mouse0 (or even event0, if you please)
instead of mouse3, etc.

the point in that would be to have 
- a more tidy XF86Config, where the Xserver :0 connects to the
  mouse0 etc (this point is minor and rather cosmetic)
- a way that a given mouse model remains the dedicated poninting
  device of a given (configured) Xserver, even after plugging and
  unplugging of your devices, in which the initialisiation order
  (and device/event number) might change as of now.
  This is actually the same as for the keyboards.

Right now i am putting together a system which (among other) uses
a userspace mechanism to determine the vt which it should bind
keyboards to. for conveniance i am useing the hotplug interface
and consider extending hotplug to return vt numbers. 

I would like to get feedback from someone more involved in these
matters. who could help me?