Greg KH <[EMAIL PROTECTED]> wrote: > > > I don't agree that this is a userspace issue. It's just not sane for a > > driver to be in an unusable state for an arbitrary length of time after > > modprobe returns. > > It is a userspace issue. If you have a static /dev there are no > problems, right? If you use udev, you need to wait for the device node > to show up, it will not be there right after modprobe returns.
OK, that's different. (grumble, mutter) It would be very convenient, tidy and sane if we _could_ arrange for modprobe to block until the device node appears though. I think devfs can do that ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
