On 18/10/05, Greg Thomas <[EMAIL PROTECTED]> wrote: > My apologies if I am confused here but that doesn't really answer the > original question, does it? I assume this solution will also work for the > other person but his question as framed was regarding assigning static > device names rather than determing the dynamically assigned device name.
Yes, the original question was about statically assigning device names. Static device can't happen unless you can make some pretty reliable guarantees about which devices are going to show up where and back it up with a way for the kernel to know which device it's really talking to. It doesn't strike me as a very wise idea to have fixed configurations for hotplug devices. What happens if you plug in another similar device? Does the first one get stomped on? Personally, I hate the fact that I now have com0 .. com15 on my windows install because of all the usb-serial devices I've plugged in. I'd much prefer it if all hot plug serial devices just used the first available comm port number. This is a matter of "what's the real problem you are trying to solve?" In this case "i have a number of USB devices which may or may not be connected at any given time, how do I provide a consistent interface to the ones that are connected?" It seems much safer to allow the kernel to notify userland (via hotplugd) that a new device just showed up at /dev/whatchamacallit and whoever's interested can now use the device. Then let userland sort out whether it was the Lexmark or the Epson printer that just got plugged in (via /etc/hotplug/attach). CK -- GDB has a 'break' feature; why doesn't it have 'fix' too?
