On Mon, Jul 06, 2009 at 11:08:10AM -0700, Peter Naulls wrote: > On Mon, Jul 6, 2009 at 11:01 AM, Alan Stern<stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Mon, 6 Jul 2009, Peter Naulls wrote: > > > > >> > >> ttyUSB3 is now missing, which was the device I was trying to use. > > > > This is correct behavior, isn't it? Your program is still running and > > still holding ttyUSB3 open, so that same minor number can't be used for > > a new device node. > > > > Dubious. It's true that I am still holding it open, but it will eventually be > let go by pppd et al. Apart from that, it's a departure from behaviour in > previous kernel versions. As Alan Stern noted, this is the same behavior that has been present for many years now. Perhaps your userspace program is not paying attention to the proper tty signals now saying that the device was removed (hangup I think.) Or perhaps the tty layer is not sending those messages anymore? > And how do I determine which interface > is the correct control interface the 3rd, 5th, 10th time it's inserted? Use the persistent device nodes in /dev/ for usb to serial devices that modern versions of udev provides you. To rely on anything else would be madness :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
