From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [RFC] coldplug - emit hotplug events from sysfs
Date: Mon, 03 Oct 2005 15:21:49 +0000 [thread overview]
Message-ID: <1128352909.7525.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20051001124943.GA26076@vrfy.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Mon, 2005-10-03 at 14:21 +0200, Kay Sievers wrote:
> To play with it, I use this stupid hack in an early init-script and
> it works without udevstart or any other coldplug logic.
> After mounting tmpfs, creating /dev/null, disabling /sbin/hotplug and
> starting udevd, it creates the tty devices, waits for the events to
> finish, then sends out all remaining events to finish asynchronously:
> ...
> # regenerate events by triggering sysfs
> for i in /sys/class/t*/*/uevent; do echo 1 > $i; done
> # wait for async tty events to finish
> while [ $(cat /proc/*/status 2> /dev/null | grep -c -E '^Name:.udevd?$') -gt 1 ]; do
> sleep 0.1
> done
>
There's a much better way to do this! If there's a guarantee that a
"write to uevent" will cause a uevent, you can simply use the udev rules
to make sure that udev has fired for each uevent you caused to be
generated.
No need to grovel for udev processes, etc.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-03 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 12:49 [RFC] coldplug - emit hotplug events from sysfs Kay Sievers
2005-10-03 10:03 ` Scott James Remnant
2005-10-03 10:29 ` Olivier Blin
2005-10-03 12:21 ` Kay Sievers
2005-10-03 13:00 ` Olivier Blin
2005-10-03 15:21 ` Scott James Remnant [this message]
2005-10-03 15:29 ` Kay Sievers
2005-10-03 16:22 ` Greg KH
2005-10-03 16:31 ` Scott James Remnant
2005-10-03 17:44 ` Olivier Blin
2005-10-03 17:49 ` Bill Nottingham
2005-10-03 17:59 ` Olivier Blin
2005-10-04 21:00 ` Greg KH
2005-10-28 20:12 ` Scott James Remnant
2005-10-28 20:14 ` Greg KH
2005-10-29 2:29 ` Alexander E. Patrakov
2005-10-29 2:43 ` Greg KH
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=1128352909.7525.4.camel@localhost.localdomain \
--to=scott@ubuntu.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).