summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-02-07 13:45:45 -0600
committerTom Zanussi <tom.zanussi@intel.com>2011-02-09 14:14:01 -0600
commit0b8fcb95dd4209d56e150d0b20133e728b22776c (patch)
tree66f8a650127eb89bc13cba8b0ad93b31c7c3801d
parent45526f5ecfd7fec22ce8022b46c311e77ee0fa9f (diff)
downloadpoky-0b8fcb95dd4209d56e150d0b20133e728b22776c.tar.gz
init-live.sh: add 'coldplug' udev trigger
Fixes [BUGID #693] The init-live.sh script starts udevd in init-live.sh:early_setup(), but doesn't account for the possibility that the root device may have already been registered by the kernel before udevd starts up. If the device is detected after udevd starts up, everything's fine - udevd gets the 'add' uevent for the device, the root image shows up at e.g. /media/sda/rootfs.img, and the boot continues. If however the device is detected before udevd starts up, udevd misses the 'add' uevent and the root image never shows up, causing it to stay in the 'waiting for removable media' loop forever. The 'udevadm trigger' command is meant to be used to avoid this situation, but init-live.sh doesn't use it. Furthermore, since the default was changed in udev 152 from 'add' to 'change', the command needs to explicity name 'add' as the action. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
-rw-r--r--meta/recipes-core/initrdscripts/files/init-live.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/recipes-core/initrdscripts/files/init-live.sh b/meta/recipes-core/initrdscripts/files/init-live.sh
index c96b1f47c3..f3e514544f 100644
--- a/meta/recipes-core/initrdscripts/files/init-live.sh
+++ b/meta/recipes-core/initrdscripts/files/init-live.sh
@@ -11,6 +11,7 @@ early_setup() {
11 mount -t proc proc /proc 11 mount -t proc proc /proc
12 mount -t sysfs sysfs /sys 12 mount -t sysfs sysfs /sys
13 udevd --daemon 13 udevd --daemon
14 /sbin/udevadm trigger --action=add
14} 15}
15 16
16read_args() { 17read_args() {