From: Rick Weber <riweber@akamai.com>
To: linux-hotplug@vger.kernel.org
Subject: udev queue never gets executed
Date: Mon, 05 Jan 2009 19:56:03 +0000 [thread overview]
Message-ID: <496265D3.8010202@akamai.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
Thanks
- --Rick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJYmXTVXWP+RUfdhERAi8rAJ0VloQYgjF9AjL10qLzV3WQfNKX5gCgp/U1
34Svzr5I1EVnrH2dShMMn/A=SJuu
-----END PGP SIGNATURE-----
next reply other threads:[~2009-01-05 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 19:56 Rick Weber [this message]
2009-01-05 20:38 ` udev queue never gets executed Kay Sievers
2009-01-05 20:46 ` Rick Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496265D3.8010202@akamai.com \
--to=riweber@akamai.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).