From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bryan Kadzban Date: Wed, 02 Jul 2008 22:12:42 +0000 Subject: Re: triggering udev rules based on the state of udevd Message-Id: <486BFD5A.70004@kadzban.is-a-geek.net> List-Id: References: <20080702151527.GA22892@nostromo.devel.redhat.com> In-Reply-To: <20080702151527.GA22892@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 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Bill Nottingham wrote: > Bryan Kadzban (bryan@kadzban.is-a-geek.net) said: >> In general, I'd say that a (poor but workable) solution would be to >> simply wait for a certain amount of time after "udevadm settle" is >> finished, then do another settle (in case new uevents happened), then >> run the assemble manually. It's not foolproof, and on a slower >> machine it could still miss disks, but it's (slightly) better than >> nothing. > > Right, but there's no way to hook into 'the queue has settled'. There is if you do this in the boot script that runs udevadm settle, after udevadm has finished. ;-) That's also the only way that I can think of to add an extra delay. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIa/1ZS5vET1Wea5wRA3fQAJ4sHue1j2fUgmcvSXRb/fZDPFk4TACfYFDV ygkOK1ob4kexWNLY7jPsiwA=ond8 -----END PGP SIGNATURE-----