initramfs-framework: drop redundant /var/lock directory creation

base-files already provides /var/lock as a symbolic link to /run/lock, and
since /run is created and mounted as tmpfs during init, there is no need
to explicitly create /var/lock within initramfs.

This avoids the following spurious error during boot:

    mkdir: can't create directory '/var/lock': No such file or directory

Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

diff --git a/meta/recipes-core/initrdscripts/initramfs-framework/init b/meta/recipes-core/initrdscripts/initramfs-framework/init
index 5dd252219aca49184e8a94c554d5c1b523b4d146..fe6e3cbf07822febcabe38b58aa1ae75668ade16 100755 (executable)
--- a/meta/recipes-core/initrdscripts/initramfs-framework/init
+++ b/meta/recipes-core/initrdscripts/initramfs-framework/init
@@ -80,8 +80,8 @@ EFI_DIR=/sys/firmware/efi  # place to store device firmware information
 # make mount stop complaining about missing /etc/fstab
 touch /etc/fstab
 
-# initialize /proc, /sys, /run/lock and /var/lock
-mkdir -p /proc /sys /run /var/lock
+# initialize /proc, /sys and /run/lock
+mkdir -p /proc /sys /run
 mount -t proc proc /proc
 mount -t sysfs sysfs /sys
 mount -t tmpfs tmpfs /run