On Thu, Dec 04, 2008 at 12:54:31AM +0100, Kay Sievers wrote: > Yeah, it looks really strange with your devices. Why put people poetry > in the device strings? :) > > But it seems to work, which is great. Here is a new version of the > serial.rules and a /lib/udev/path_id which needs to be replaced. > > Can you try that again on your "collection"? :) Here you go. I'm not so sure the "by-path" is that useful, as it has the ttyUSB number in the name, which can be different from boot-to-boot. How about putting the usb path in there and not truncate it? thanks, greg k-h $ tree /dev/serial/ /dev/serial/ |-- by-id | |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0 | |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1 | |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2 | |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3 | |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8 | |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9 | |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10 | |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11 | `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7 `-- by-path |-- pci-0000:00:1d.2-usb-0:ttyUSB7-port0 -> ../../ttyUSB7 |-- pci-0000:00:1d.7-usb-0:ttyUSB0-port0 -> ../../ttyUSB0 |-- pci-0000:00:1d.7-usb-0:ttyUSB1-port1 -> ../../ttyUSB1 |-- pci-0000:00:1d.7-usb-0:ttyUSB10-port2 -> ../../ttyUSB10 |-- pci-0000:00:1d.7-usb-0:ttyUSB11-port3 -> ../../ttyUSB11 |-- pci-0000:00:1d.7-usb-0:ttyUSB2-port2 -> ../../ttyUSB2 |-- pci-0000:00:1d.7-usb-0:ttyUSB3-port3 -> ../../ttyUSB3 |-- pci-0000:00:1d.7-usb-0:ttyUSB8-port0 -> ../../ttyUSB8 `-- pci-0000:00:1d.7-usb-0:ttyUSB9-port1 -> ../../ttyUSB9 -- 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