On Mon, 6 Jul 2009, 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. Not at all; the kernel has always behaved this way. Maybe it's not a good way, but it hasn't changed. > And how do I determine which interface > is the correct control interface the 3rd, 5th, 10th time it's inserted? I don't know. In fact, I don't even know how you can determine the correct interface the first time. After all, if you had another USB serial device plugged in earlier then all the ttyUSB numbers would get bumped up correspondingly. The information may be available in sysfs. It certainly is available in the system log, but digging it out isn't easy. > I don't pretend to be an expert on device allocation etc, in the kernel, > so please correct me here, but this doesn't seem the best. What would you prefer? And what would you do if you had 2 of these devices? Alan Stern -- 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
