DJ Lucas wrote: > On 05/16/2011 12:59 AM, Bryan Kadzban wrote: >> DJ Lucas wrote: >>> <stuff about settle being broken> >> I see some traffic on linux-hotplug about this as well, so it looks like >> it's not LFS-specific, at least. (Arch and Debian have both had bugs >> reported about this.) The messages from Kay so far seem encouraging, as >> well. >> >> ...Oh, and I see the message from you there, too. OK, never mind. :-) >> >> It's looking like it'll get sorted out soon. >> > I committed a patch to patches/udev/udev-168-settle-1.patch, should be > added to the book. > > Also, while on the subject, in the udev README file they mention this > change: > > dj [ lsb-bootscripts ]$ diff -au etc/init.d/udev /etc/init.d/udev > --- etc/init.d/udev 2011-05-14 22:17:45.000000000 -0500 > +++ /etc/init.d/udev 2011-05-18 12:08:33.000000000 -0500 > @@ -73,7 +73,8 @@ > > # Now traverse /sys in order to "coldplug" devices that have > # already been discovered > - /sbin/udevadm trigger --action=add > + /sbin/udevadm trigger --action=add --type=subsystems > + /sbin/udevadm trigger --action=add --type=devices > > # Now wait for udevd to process the uevents we triggered > /sbin/udevadm settle > > Seems logical, any reason not to?
From the manpage, --type=devices is the default, so this is a superset of what we're triggering today. So yes, and oops. (Looks like we should have been doing this for a while now.) :-)
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
