Hello, I try to create a udev-rule for the USB-Devices produced by our company. Espacially one device drives me crazy. This is a board connects via USB, the kernel creates a tty (/dev/ttyUSB?). Other USB-Devices can be connected to this "baseboard". To create a unique Devicenode to that Baseboard I have to create a UDEV-Rule. For the other devices connected to that baseboard a rule already exists. Here is the ruleset for our devices: =============================================== # rule for io-interfaces SUBSYSTEMS== "usb", KERNEL=="ttyUSB[0-9]*", ATTR{idVendor}=="1dfb", RUN+="/usr/uti/udevscript usbmodul %k $env{ID_SERIAL_SHORT}" # additional rule for io-interfaces to read with control485 SUBSYSTEMS=="tty", KERNEL=="ttyUSB[0-9]*", ACTION=="add", RUN+="/usr/uti/udevscript-485 usbmodul %k $env{ID_SERIAL_SHORT}" SUBSYSTEMS=="tty", KERNEL=="ttyUSB[0-9]*", ACTION=="remove", RUN+="/usr/uti/marco-udevscript-485 usbmodul_remove %k" # USBSTICK SUBSYSTEMS== "usb", KERNEL=="sd[a-z]1", RUN+="/usr/uti/marco-udevscript usbstick %k" SUBSYSTEMS== "usb", KERNEL=="sd[a-z]", RUN+="/usr/uti/marco-udevscript usbstick_device %k" # PCAN SUBSYSTEMS== "usb", ATTR{idVendor}=="0c72", ATTR{idProduct}=="000c", RUN+="/usr/uti/udevscript pcan" # 2a-Board SUBSYSTEMS=="usb", KERNEL="ttyUSB[0-9]*", ATTRS{idVendor}=="1dfb", ATTRS{idProduct}=="0007", SYMLINK+="/dev/2a/%k" ================================================ Here is a "/sbin/udevadm info --query=all --attribute-walk --name=/dev/ttyUSB0" for that device (it is reachable over /dev/ttyUSB0): http://pastebin.com/B8YrQSxm I disconnect and connect that device....but nothing is created under /dev/2a. Any hints about this ruleset? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds@xxxxxxxx Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- 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