From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Blin Date: Mon, 03 Oct 2005 17:59:26 +0000 Subject: Re: [RFC] coldplug - emit hotplug events from sysfs Message-Id: List-Id: References: <20051001124943.GA26076@vrfy.org> In-Reply-To: <20051001124943.GA26076@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Bill Nottingham writes: > Olivier Blin (oblin@mandriva.com) said: >> > Ok, that's just as hacky as grovelling around in ps I guess, but at >> > least it has the advantage that there's no possibility of no udev >> > processes having been started by the next line of shell - which there is >> > with your example. >> > >> > There's almost certainly a more elegant way, but basically mark the >> > events you're waiting for and wait for them all to come back. >> >> We could have a lock directory, in which a lock file would be added for >> each event (using the full path with '/' replaced by '%' for example). >> This lock file would be removed once udev is done processing the event. >> But is it easy to remove a lock file when a PROGRAM or RUN rule is >> used? Maybe by catching signals of this program. > > Realistically, how often are you doing udev coldplug with a writable > system filesystem? I'd suspect at least in our case, any coldplug > would be well before the root fs is read/write. That's right, coldplug is often done when the root fs isn't writable yet. But it isn't really a problem, we could use something like /dev/.udevdb/, for example /dev/.udevlock/ -- Olivier Blin Mandriva ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.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