Re: udev queue never gets executed

[Rick Weber <riweber@akamai.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I see the basic message that the module has been loaded.  But that's it.
 When I run udevtrigger, I see a ton of other messages execute,
including  the commands I expect to be executed from the insertion of
the md device.

Actually, as part of my "hack", I've done an:

ln -s /etc/rcS.d/S19udevtrigger /sbin/udevtrigger

After that, I don't need to modprobe md_mod any more.  The kernel picks
up the modules correctly.

- --Rick

Kay Sievers wrote:
> On Mon, Jan 5, 2009 at 20:56, Rick Weber <riweber@akamai.com> wrote:
>> Hopefully a quick question.  I'm working on a very hacked kernel (based
>> off of Ubuntu LTS), and trying to get RAID support working.
>>
>> Long story short, after I do a "modprobe md_mod", I need to issue
>> /sbin/udevtrigger to have the udev rules execute.  Running udevd with
>> the debug options on pretty much verifies that the system doesn't want
>> to automatically execute the rules after the modprobe, and won't execute
>> until I do the udevtrigger call.
>>
>> Can you point me in a general direction on where to look?  Is it
>> something as simple as udev is disable, a named pipe needs to get
>> created, or something else?
> 
> Which events do you expect to run? If you run "udevmonitor" while
> loading the module, you see the events the kernel generates.
> 
> Kay
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJYnHAVXWP+RUfdhERAnkTAJ0QY3JBMepxuKYVG0JZEU5HZXvN3QCghKie
waNEmMEY7wlhJXQs3h5g99I=M845
-----END PGP SIGNATURE-----