From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Zoz Date: Thu, 25 Aug 2005 06:43:27 +0000 Subject: Re: udevsynthesize as a udevstart+coldplug replacement Message-Id: <20050825064327.GZ3958@suse.de> List-Id: References: <20050823191542.GA29091@vrfy.org> In-Reply-To: <20050823191542.GA29091@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: linux-hotplug@vger.kernel.org On Wed, Aug 24, Marco d'Itri wrote: > On Aug 24, Kay Sievers wrote: > > > > What about a new udevcontrol parameter which makes it block until the > > > udevd is done? > > What state is "udevd is done"? No event in the queue? > Unless you can think about something smarter, yes. No UDEV_SYNTHESIZE event in the queue. > > > This way if needed it could be run in a different init > > > script to allow parallel processing at boot time. > > Hmm, what do you mean? Who waits for whom? > multiple init scripts would depend on the udev-done (or something like > this) init script, which will not terminale until udevcontrol will. > This way other init scripts would be able to continue working without > needing to wait for udev. > Or maybe it's not worth the effort, because they would need to use > /some/ device node anyway. Why not make the init scripts wait individually for whatever they need? -- ciao, christian 睡眠不足はいい仕事の敵だ。 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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