>> I can't test this right now, but doesn't quite understand what this will do. Does >> this solve the problem where the ttyUSBx interface changes and make it always be >> the >> same? >> >> If I have e.g. ttyUSB1,ttyUSB2 and ttyUSB3 devices, what will be the symlink to >> ttyUSB1 (used for pppd), which only interests? > > If you have different devices, all links in /dev/serial/by-id/ will > stay the same, regardless of the order, or the USB hub/port they are > plugged in. If you have identical devices, without any serial number, > only the controller/hub/port number can be used to distinguish them. > The /dev/serial/by-id/ links will overwrite each other for identical > devices, and /dev/serial/by-path/ must be used. > >> And how about the other thing, how to >> trigger some wvdial connect script via udev at the same time the >> ttyUSB1 thing comes up? > > You can match on properties of the device, or even the link name > itself with SYMLINK=="serial/by-..." with udev rules, that come after > the 60-*.rules. These rules can trigger anything you need. > > Kay OK, thanks, I will try these when I have time. My udev is version udev-118-1.fc8, any idea if this works with it? -- Best Regards, Jar -- 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
