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
On Fri, 14.02.14 13:52, Laércio de Sousa (lbsous...@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
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?
CANTATE DOMINO CANTICUM NOVUM
QUIA
On Fri, Feb 14, 2014 at 5:25 PM, Laércio de Sousa lbsous...@gmail.com wrote:
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
On 15/02/2014 01:52 , Laércio de Sousa 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
