On Wed, 2005-04-06 at 13:25 -0400, Jeff Spaleta wrote:
On Apr 6, 2005 12:26 PM, Ivan Gyurdiev <ivg2(a)cornell.edu>
wrote:
> What was wrong with it prior to this work - isn't this supposed to
> happen at modprobe time anyway?
udev adds a wrinkle. My understanding is that sometimes... udev
doesn't finish creating the needed /dev/ entries before the modprobe
script fires.
This is pretty much a feature of the Linux 2.6 kernel and udev combo.
Search the lkml for threads about why this is so.
I don't think udev has a mechanism to communicate back
to modprobe with a "hey I'm done, run your install scripts now." So
as a result some people/hardware see this problem and some
people/hardware doesn't.
This is exactly why we have the dev.d notifiers.
Cheers,
David