Your message dated Tue, 16 May 2006 14:24:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367487: udev: persistent-input.rules is not catch-all
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: udev
Version: 0.091-2
Severity: normal
At least on 2.6.16.16, it seems..
KERNEL=="event*", \
ENV{ID_BUS}=="?*", ENV{ID_SERIAL}=="?*", ENV{ID_CLASS}=="?*", \
SYMLINK+="input/by-id/$env{ID_BUS}-$env{ID_SERIAL}-event-$env{ID_CLASS}"
..is not catch-all.
For example, I had to do..
KERNEL=="event[0-9]*", SYSFS{name}=="*dvb*|*DVB*|* IR *",
SYMLINK+="input/remote"
.. for the event file for the remote control of a usb dvb device.
or..
KERNEL=="event[0-9]*", SYSFS{name}=="*lpsPS*", SYMLINK+="input/mousepad"
.. for the event* of the mousepad.
This behavior is quite problematic when using programs that utilise evdev since
event file numbering differs each time replugging of a usb device is done.
--- End Message ---
--- Begin Message ---
On May 16, michaelm <[EMAIL PROTECTED]> wrote:
> ..is not catch-all.
It was never supposed to be, by design persistent links are only
generated for known types of devices.
> .. for the event file for the remote control of a usb dvb device.
Support for more device types will appear in the next upload.
path_id now should support all the common input devices buses, e.g.:
lrwxrwxrwx 1 root root 9 May 16 14:17
/dev/input/by-path/platform-i8042-serio-1-event-kbd -> ../event0
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
