Use "udevadm trigger --type=failed" instead of "--retry-failed", since the latter is gone as of udev-146. The former works in earlier versions as well, at least as far back as -143 (which includes the current book version).

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9049 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

bootscripts/ChangeLog

@@ -1,3 +1,8 @@
+2009-08-14  Bryan Kadzban <bryan@linuxfromscratch.org>
+   * lfs/init.d/udev_retry: Use "udevadm trigger --type=failed", which
+     apparently replaced "--retry-failed" some time ago.  "--retry-failed" is
+     removed in udev-146.
+
 2009-01-02  Bruce Dubbs <bdubbs@linuxfromscratch.org>
    * lfs/init.d/functions:
    * lfs/sysconfig/network-devices/ifup: 

bootscripts/lfs/init.d/udev_retry

@@ -29,7 +29,7 @@ case "${1}" in
 		done
 
 		# Re-trigger the failed uevents in hope they will succeed now
-		/sbin/udevadm trigger --retry-failed
+		/sbin/udevadm trigger --type=failed
 		
 		# Now wait for udevd to process the uevents we triggered
 		/sbin/udevadm settle