On Mon, Mar 21, 2005 at 04:43:18PM -0800, Andrew Morton wrote: > 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)
Heh, the sound people went through the same grumblings a few months ago :) > 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 ;) devfs _can_ do that, as it waits on the register block device to create the node. All udev can do is act apon the call to hotplug as fast as it can (in the correct order). The kernel issues the call and then returns, causing modprobe to return. The distros that use udev have already all worked out these issues with their init scripts and such, so it shouldn't be an issue anymore. Jon, what distro are you using? thanks, greg k-h - 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/
