From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: waiting for an unknown set of udev /dev entries to complete
Date: Sun, 20 Nov 2005 23:53:29 +0000 [thread overview]
Message-ID: <20051120235329.GB28968@vrfy.org> (raw)
In-Reply-To: <20051118223045.GA28401@us.ibm.com>
On Sun, Nov 20, 2005 at 09:10:35PM +0100, Pozsar Balazs wrote:
> On Sun, Nov 20, 2005 at 07:03:57AM +0100, Kay Sievers wrote:
> > On Fri, Nov 18, 2005 at 02:30:45PM -0800, Patrick Mansfield wrote:
> > > Any ideas on the best way to wait for udev to finish handling a set of
> > > hotplug events?
> >
> > I have changes in my udev tree, to export the udevd event queue. It
> > will probably be in 076 - if it works as expected. For every queued
> > or running event, a symlink in /dev/.udev/queue/ is created and removed
> > after the udev event process has exited. For all failing udev events,
> > the queue files are moved to /dev/.udev/failed.
> >
> > We want this for coldplug after bootup, to try to trigger failed events
> > again, if requirements are fulfilled only at a later stage of the boot
> > process.
>
> What failed events do you think of? I suppose you really need this for
> some cases, and I can't imagine what it is.
For checkpointing the boot process. Simplest example is that programs
needed for some devices to set-up are not on the root filesystem. These
events will fail, cause RUN will fail with the coldplug calls. The failed
events can be tried again, after the localfs's are mounted.
We will see what weird things we will need to work around, to support
all the insane options people invented in the unix history.
> Side note about coldplug: wouldn't it be nicer if udevd would:
> - trigger all events using the uevent files under /sys
> - wait for these events to arrive and to finish
> - _then_ fork and daemonize itself.
That would make no difference, besides hardcoding the event trigger
order into the daemon.
> This would mostly eliminate the need to hack ugly scripts around udev to
> watch its queue, wait for devices on boot etc.
Well these scripts are not ugly, it's pretty simple and flexible. Be
sure, we have much uglier things to handle and we will need the
flexibility and control over the event generation.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&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:[~2005-11-20 23:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 22:30 waiting for an unknown set of udev /dev entries to complete Patrick Mansfield
2005-11-20 6:03 ` Kay Sievers
2005-11-20 17:25 ` Patrick Mansfield
2005-11-20 18:23 ` Kay Sievers
2005-11-20 20:10 ` Pozsar Balazs
2005-11-20 20:23 ` Marco d'Itri
2005-11-20 23:32 ` Kay Sievers
2005-11-20 23:53 ` Kay Sievers [this message]
2005-11-21 0:01 ` Marco d'Itri
2005-11-22 23:13 ` Kay Sievers
2005-11-23 8:26 ` Scott James Remnant
2005-11-23 10:54 ` Pozsar Balazs
2005-11-23 16:27 ` Harald Hoyer
2005-11-23 16:50 ` Kay Sievers
2005-11-23 17:25 ` Pozsar Balazs
2005-11-23 17:46 ` Kay Sievers
2005-11-23 18:16 ` Pozsar Balazs
2005-11-23 18:39 ` Kay Sievers
2005-11-23 21:33 ` Patrick Mansfield
2005-11-28 22:09 ` Pozsar Balazs
2005-11-29 10:44 ` Kay Sievers
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=20051120235329.GB28968@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).