From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Date: Tue, 18 Apr 2006 03:02:26 +0000 Subject: Re: Integrate udevsettle with udevtrigger? Message-Id: <444456C2.4040905@ums.usu.ru> List-Id: References: <444421CE.3030206@kadzban.is-a-geek.net> In-Reply-To: <444421CE.3030206@kadzban.is-a-geek.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Bryan Kadzban wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > It seems to me that udevtrigger and udevsettle are strongly related > (generate all the uevents, then wait for them to finish -- this seems > like it's is all part of the same "task"). Therefore I don't really see > any reason to run udevtrigger without udevsettle. I doubt any distro's > bootscripts are going to run the one without the other, for instance, > but even running udevtrigger manually should (IMO) wait for events to > settle out. > > Would it make sense to anyone else to integrate the two programs, by > adding an option to udevtrigger that would tell it to wait? It doesn't make sense to remove udevsettle as a separate program. Reason: it is needed on its own in the udev_retry script. See http://wiki.linuxfromscratch.org/lfs/ticket/1769. -- Alexander E. Patrakov ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ 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