Bug#336297: udev: Doesn't appear to run RUN= entries on startup

2005-10-30 Thread Mark Brown
On Sat, Oct 29, 2005 at 11:15:18PM +0200, Marco d'Itri wrote: On Oct 29, Mark Brown [EMAIL PROTECTED] wrote: (note the test for $ACTION - this is why I didn't bother specifying it in the udev rule.) Yes, but if you test it in the rule you save a fork+exec if it does not match. Ah, OK.

Bug#336297: udev: Doesn't appear to run RUN= entries on startup

2005-10-30 Thread Marco d'Itri
On Oct 30, Mark Brown [EMAIL PROTECTED] wrote: Or else you can just install a 2.6.15 kernel which supports /dev/bus/usb/ and does not need a script. Presumably I would still need a script in order to propagate things into procfs until user space knows about the new /dev directory? The

Bug#336297: udev: Doesn't appear to run RUN= entries on startup

2005-10-29 Thread Mark Brown
Package: udev Version: 0.071-1 Severity: normal I have the following rule in my /etc/udev/rules.d/local.rules: SYSFS{idVendor}==04e6, SYSFS{idProduct}==e003, RUN+=/etc/hotplug/usb/gnupg-ccid When I hotplug this device at run time the referenced script is executed. However, when I boot the

Bug#336297: udev: Doesn't appear to run RUN= entries on startup

2005-10-29 Thread Marco d'Itri
tag 336297 unreproducible moreinfo thanks On Oct 29, Mark Brown [EMAIL PROTECTED] wrote: I have the following rule in my /etc/udev/rules.d/local.rules: SYSFS{idVendor}==04e6, SYSFS{idProduct}==e003, RUN+=/etc/hotplug/usb/gnupg-ccid It's supposed to work. At least, it does for me. BTW, you

Bug#336297: udev: Doesn't appear to run RUN= entries on startup

2005-10-29 Thread Mark Brown
On Sat, Oct 29, 2005 at 01:36:53PM +0200, Marco d'Itri wrote: It's supposed to work. At least, it does for me. BTW, you should add a BUS statement and definitely ACTION==add. I changed the rule to: BUS==usb, SYSFS{idVendor}==04e6, SYSFS{idProduct}==e003, ACTION==add,