linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: linux-hotplug@vger.kernel.org
Subject: udev 145, when are events fully processed?
Date: Sat, 01 Aug 2009 19:55:10 +0000	[thread overview]
Message-ID: <4A749D9E.3020709@lbsd.net> (raw)

Hi Guys,

Trying to figure something out here, using the following I'm seeing a
delay in the creation of block devices in /dev ...

# trigger the sorted events
echo -e '\000\000\000\000' > /proc/sys/kernel/hotplug

rm -fr /dev/.udev > /dev/null 2>&1
mkdir -p /dev/.udev > /dev/null 2>&1
/sbin/udevd

# Not entirely sure what this is for
/sbin/udevadm control --env=STARTUP=1
/sbin/udevadm trigger
/sbin/udevadm settle
# Nor sure what this does
/sbin/udevadm control --env=STARTUP

I think my problem is, while all the events have been sent to udevd
there is a delay if I do a  "fsck LABEL=root" straight on say the next
line,  a "ls" shows that none of the block devices exist until a second
or two later. A sleep 5 before my "ls" works around this and the block
devices show up.

Any ideas how I can determine once all udev events have finished
processing so I can continue boot?


Kind Regards
Nigel

             reply	other threads:[~2009-08-01 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 19:55 Nigel Kukard [this message]
2009-08-07 12:26 ` udev 145, when are events fully processed? Harald Hoyer
2009-08-07 12:56 ` Nigel Kukard
2009-08-07 14:15 ` Alan Jenkins
2009-08-07 14:48 ` Nigel Kukard
2009-08-07 15:34 ` Kay Sievers
2009-08-07 16:00 ` Alan Jenkins
2009-08-07 16:10 ` Nigel Kukard
2009-08-07 16:24 ` Kay Sievers
2009-08-07 16:40 ` Nigel Kukard

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=4A749D9E.3020709@lbsd.net \
    --to=nkukard@lbsd.net \
    --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).