Bryan Kadzban wrote: > Or, actually, what happens if you move 70-persistent-net.rules out to > /dev/.udev/rules.d/, then do what we have in the udev_retry bootscript? > (That is, cat the file out of /dev/.udev/rules.d, and append the result > into /etc/udev/rules.d, then rm the version in /dev/.udev/rules.d as a > separate operation.) At what point is the message logged, if it's > logged in that operation anywhere?
The message gets logged as soon as I move 70-persistent* to /dev/.udev/rules.d. > If you have console access, you might also try booting with > init=/bin/bash (after deleting the generated rules) and running each > bootscript individually. This should show which script is causing the > log message at least. (Just be sure that if you get to the point of > mounting anything read-write, you unmount it before rebooting.) It's the S50udev_retry script that triggers it. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
