Re: udev is too slow creating devices

["Alexander E. Patrakov" <patrakov@ums.usu.ru>]

Greg KH wrote:
> 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.

Hm, why should _I_ sleep and spin after modprobe, without even knowing 
if the node will appear at all, when you can include the "modprobe" 
wrapper script with udev source package.

This wrapper should call modprobe.orig with original arguments, and then 
call udev for /sys entries that appeared (or just run udevstart), and 
only then return. Yes, this will result in duplicate hotplug events 
(synthetic + real) being delivered to udev, but it solves the problem 
with modprobe once, for all programs, and in compatible way.

-- 
Alexander E. Patrakov