[OE-core] [PATCH 2/2] initramfs-framework: base: Ensures /run/lock is available
Otavio Salvador
otavio at ossystems.com.br
Mon Jun 20 18:23:53 UTC 2016
Depending on the module we use, the /run/lock may be required. This
creates it as part of initial setup and thus makes it available for
every sub module.
Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
---
meta/recipes-core/initrdscripts/initramfs-framework/init | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/init b/meta/recipes-core/initrdscripts/initramfs-framework/init
index 204f237..37527a8 100755
--- a/meta/recipes-core/initrdscripts/initramfs-framework/init
+++ b/meta/recipes-core/initrdscripts/initramfs-framework/init
@@ -76,8 +76,8 @@ MODULES_DIR=/init.d # place to look for modules
# make mount stop complaining about missing /etc/fstab
touch /etc/fstab
-# initialize /proc, /sys and /var/lock
-mkdir -p /proc /sys /var/lock
+# initialize /proc, /sys, /run/lock and /var/lock
+mkdir -p /proc /sys /run/lock /var/lock
mount -t proc proc /proc
mount -t sysfs sysfs /sys
--
2.8.3
More information about the Openembedded-core
mailing list