Re: udev is too slow creating devices

[Greg KH <greg@kroah.com>]

On Tue, Sep 14, 2004 at 11:45:52PM +0200, Marco d'Itri wrote:
> On Sep 14, Greg KH <greg@kroah.com> wrote:
> 
> > What's wrong with the /etc/dev.d/ location for any type of script that
> > you want to run after a device node has appeared?  This is an
> > application specific issue, not a kernel issue.
> The problem is that since most distributions cannot make udev usage
> mandatory, this would require duplicating in the init script and in the
> dev.d script whatever needs to be done with the device.

Well, that sounds like a distro problem then, not a kernel or udev one :)

> Then there are the issues of scripts needing programs in /usr, which may
> not be mounted when the module is loaded, or which are interactive and
> need console access (think fsck).

True, so sit and spin and sleep until you see the device node.  That's
how a number of distros have fixed the fsck startup issue.

> Basically asyncronous creation of devices requires a ground up redesign
> of the init scripts of a distribution. I'm not claiming that this is not
> possible, but it's not going to happen soon.

Well, it needs to go that way, as the kernel moves toward not providing
the device node right when modprobe returns with the advent of
multi-threading device discovery and such.  That's why the /etc/dev.d
heirachy was created, it's not dependant on udev to provide such a
solution.  I suggest that distros that do not use udev (of which Debian
is slowly becoming a miniority) create a tool that causes /etc/dev.d
events for a static /dev tree.

thanks,

greg k-h