From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 15 Oct 2004 22:01:38 +0000 Subject: Re: waiting for udevstart Message-Id: <20041015220138.GB27196@kroah.com> List-Id: References: <20041015214333.GA26151@nostromo.devel.redhat.com> In-Reply-To: <20041015214333.GA26151@nostromo.devel.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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... > 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. thanks, greg k-h ------------------------------------------------------- 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