From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: waiting for udevstart
Date: Fri, 15 Oct 2004 22:54:28 +0000 [thread overview]
Message-ID: <20041015225428.GA1075@vrfy.org> (raw)
In-Reply-To: <20041015214333.GA26151@nostromo.devel.redhat.com>
On Fri, Oct 15, 2004 at 03:01:38PM -0700, Greg KH wrote:
> On Fri, Oct 15, 2004 at 05:43:33PM -0400, Bill Nottingham wrote:
> > udevstart is called on startup to populate /dev.
> >
> > However, all it does is generate udev events - which means
> > that when udevstart exits, /dev isn't necessarily populated
> > at all.
>
> Are you sure? In looking at the most recent code (remember, udevstart
> is a symlink to udev now) I don't see any exec or fork() path when
> udevstart is running. But I might be missing something...
Right, we just prepare the list of devices to work on, and walk over it
without any external call. Just one binary. During that walk the dev.d/
scripts will be called.
> > You could do a hack like:
> >
> > - generate a list of all the events you're going to create
> > - write a dev.d script that waits for the last one
> > - while (1) sleep(500);
> > - have that dev.d script kill udevstart
> >
> > But that's gross.
>
> That is.
>
> > Any better suggestions?
>
> Make udevstart not return until it is done. I think that's what it does
> today. But if not, I'll gladly accept patches to make it do so.
No, it will not return until the last node is created!
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-15 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 21:43 waiting for udevstart Bill Nottingham
2004-10-15 21:54 ` Bill Nottingham
2004-10-15 22:01 ` Greg KH
2004-10-15 22:46 ` Marco d'Itri
2004-10-15 22:54 ` Kay Sievers [this message]
2004-10-15 23:03 ` Kay Sievers
2004-10-15 23:24 ` Marco d'Itri
2004-10-15 23:40 ` Kay Sievers
2004-10-15 23:45 ` Marco d'Itri
2004-10-16 2:54 ` Bill Nottingham
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=20041015225428.GA1075@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).