[systemd-devel] [PATCH] Ship new udev rules file to create per-seat symlinks for input devices

Laércio de Sousa lbsousajr at gmail.com
Fri Feb 14 08:25:14 PST 2014

Good point.

I used to append a $env{MINOR} to symlink names to avoid such ambiguities.
A side effect of this approach is that symlink names would change every
time the device is plugged in a different USB port, for example.

Would it be enough for you?



2014-02-14 13:58 GMT-02:00 Lennart Poettering <lennart at poettering.net>:

> On Fri, 14.02.14 13:52, Laércio de Sousa (lbsousajr at gmail.com) wrote:
> > This rules file tells udev to create symlinks for input devices
> > (keyboard and mouse, at this moment) separated by seat, so it could
> > be easier for one to get quickly the devpath of a given input
> > device attached to a given seat.
> >
> > Example: the keyboard attached to seat-foo will receive a symlink
> > with path /dev/input/by-seat/seat-foo.kbd-event
> >
> > It can be very handful specially for Xephyr-based multiseat setups,
> > where input devpaths must be passed via command line options
> > like -keybd and -mouse.
> Hmm, modern systems tend to have multiple keyboards and mice. For
> example, mine has a touchscreen and a touchpad as mouse and a a couple
> acpi devices plus a real kbd, plus some laptop-specific keys all exposed
> as keyboards. Trying to create a single symlink for all of this appears
> to be doomed to fail?
> Lennart
> --
> Lennart Poettering, Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140214/e73e6400/attachment-0001.html>

More information about the systemd-devel mailing list