From: "Marty Leisner" <leisner@rochester.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: udev synchronization
Date: Fri, 25 Jan 2008 21:38:14 +0000 [thread overview]
Message-ID: <200801252138.m0PLcEEs017177@dell2.home> (raw)
Didn't see much about this...
When I'm modprobe a loopAES driver, then doing a bunch of loop mounts, the
loop devices aren't present when I start associating the loop devices with the block devices.
I'm using udev-082 (since this seems to work with 2.6.10 and 2.6.20 kernels
which I'm supporting.
There's a udevsettle which seems to handle the synchronization. Its not
in udev-082. Maybe its a good idea...it probably makes sense to add a flag
to modprobe so modprobe returns when its "safe" to use the devices...
What I did at one time was stick a sleep in (ugh).
Someone else stuck in a udevstart (which seems to do the trick).
Any problem running udevstart while udevd is running?
marty
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2008-01-25 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200801252138.m0PLcEEs017177@dell2.home \
--to=leisner@rochester.rr.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