On Tue, Feb 10, 2009 at 18:04, Yan Seiner <yan@xxxxxxxxxx> wrote: > On Tue, February 10, 2009 7:29 am, Kay Sievers wrote: >> On Tue, Feb 10, 2009 at 16:19, Yan Seiner <yan@xxxxxxxxxx> wrote: >>> I have a device that presents itself as both a /dev/input/mouise and >>> /dev/input/event. >>> >>> The mouse: >>> >>> looking at device '/class/input/input10/mouse6': >>> KERNEL=="mouse6" >>> SUBSYSTEM=="input" >>> DRIVER=="" >> >>> The event: >>> >>> looking at device '/class/input/input10/event10': >>> KERNEL=="event10" >>> SUBSYSTEM=="input" >>> DRIVER=="" >> >>> The *only* difference between the two is the KERNEL== line. I need to >>> create a symlink to both the mouse and the event. I tried this: >> >> Use the links in: /dev/input/by-id/? >> >> They look like this for a USB mouse here: >> $ tree /dev/input/by-id/ >> /dev/input/by-id/ >> |-- usb-Logitech_USB-PS_2_Optical_Mouse-event-mouse -> ../event8 >> `-- usb-Logitech_USB-PS_2_Optical_Mouse-mouse -> ../mouse1 > Hah! Won't quite work as I have 2 of these, but I can match on the > ID_PATH env var! That's what /dev/input/by-path/ is for: /dev/input/ |-- by-id | |-- usb-Logitech_USB-PS_2_Optical_Mouse-event-mouse -> ../event6 | `-- usb-Logitech_USB-PS_2_Optical_Mouse-mouse -> ../mouse1 |-- by-path | |-- pci-0000:00:1d.2-usb-0:1:1.0-event-mouse -> ../event6 | |-- pci-0000:00:1d.2-usb-0:1:1.0-mouse -> ../mouse1 | |-- platform-i8042-serio-0-event-kbd -> ../event0 | |-- platform-i8042-serio-1-event-mouse -> ../event1 | |-- platform-i8042-serio-1-mouse -> ../mouse0 | `-- platform-pcspkr-event-spkr -> ../event2 ... Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
