From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: cold plugging
Date: Fri, 13 Jan 2006 16:23:51 +0000 [thread overview]
Message-ID: <43C7D417.3040807@ums.usu.ru> (raw)
In-Reply-To: <200601131415.30207.treeve@scarlet.be>
Kay Sievers wrote:
>I'm using this:
> list=$(echo /sys/bus/*/devices/*/uevent)
> list="$list $(echo /sys/class/*/*/uevent)"
> list="$list $(echo /sys/block/*/uevent /sys/block/*/*/uevent)"
> for i in $list; do
> case "$i" in
> */device/uevent|*\**)
> continue
> ;;
> */class/mem/*|*/class/tty/*)
> first="$first $i"
> ;;
> */block/md*)
> last="$last $i"
> ;;
> */*)
> default="$default $i"
> ;;
> esac
> done
>
> # trigger the sorted events
> for i in $first $default $last; do
> echo "add" > "$i"
> done
>
>
Why sort the events? They arrive at udevd in random order anyway.
>To wait for the events to finish (if you need to), I do:
> loop00
> while test -d /dev/.udev/queue; do
> sleep 0.1;
> test "$loop" -gt 0 || break
> loop=$(($loop - 1))
> done
>
>
USB uevents easily get past this loop. I have a check in my script that
sleeps 2 seconds after that and reports all new uevents in those 2
seconds as possible bugs.
--
Alexander E. Patrakov
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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
next prev parent reply other threads:[~2006-01-13 16:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 12:17 cold plugging Treeve Jelbert
2006-01-13 12:32 ` Kay Sievers
2006-01-13 16:23 ` Alexander E. Patrakov [this message]
2006-01-13 18:47 ` Darren Salt
2006-01-13 18:52 ` Greg KH
2006-01-13 19:13 ` Scott James Remnant
2006-01-13 19:15 ` Marco d'Itri
2006-01-13 20:08 ` Darren Salt
2006-01-13 23:29 ` Pozsar Balazs
2006-01-13 23:53 ` Greg KH
2006-01-14 5:00 ` Alexander E. Patrakov
2006-01-14 5:57 ` Alexander E. Patrakov
2006-01-14 8:45 ` Pozsar Balazs
2006-01-14 12:48 ` Kay Sievers
2006-01-14 13:08 ` Kay Sievers
2006-01-14 13:10 ` Alexander E. Patrakov
2006-01-14 13:27 ` Kay Sievers
2006-01-14 16:28 ` Alexander E. Patrakov
2006-01-15 4:13 ` Dmitry Torokhov
2006-01-15 22:44 ` Aras Vaichas
2006-01-16 12:36 ` Kay Sievers
2006-01-16 12:53 ` Kay Sievers
2006-01-16 12:59 ` Olivier Blin
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=43C7D417.3040807@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).