I can just repeat what I said in my last message, it seems important to me: If I modify /etc/init.d/udev around line 68 like this:
echo BEFORE
sleep 5
# Fix permissions and missing symlinks/programs for devices made in
# initramfs, and catch up on everything we missed
log_begin_msg "Loading hardware drivers..."
/sbin/udevadm trigger
if /sbin/udevadm settle; then
log_end_msg 0
else
log_end_msg $?
fi
echo AFTER
sleep 5
I can still see "BEFORE" appearing on the screen, but it will reboot before "AFTER" appears. So the reboot occurs while execution of " /sbin/udevadm trigger". Does anybody else observe this?
my kernel is now 2.6.28-15-generic on kubunty jaunty 64 bit.
I can just repeat what I said in my last message, it seems important to me: If I modify /etc/init.d/udev around line 68 like this:
echo BEFORE
sleep 5
# Fix permissions and missing symlinks/programs for devices made in
# initramfs, and catch up on everything we missed
log_begin_msg "Loading hardware drivers..."
/sbin/udevadm trigger
if /sbin/udevadm settle; then
log_end_msg 0
else
log_end_msg $?
fi
echo AFTER
sleep 5
I can still see "BEFORE" appearing on the screen, but it will reboot before "AFTER" appears. So the reboot occurs while execution of " /sbin/udevadm trigger". Does anybody else observe this?
my kernel is now 2.6.28-15-generic on kubunty jaunty 64 bit.