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

(From OE-Core rev: 24629a0e81291900edf0967bb218ba51dfa90ce9)

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>
This commit is contained in:
Ricardo Salveti 2025-10-17 15:51:12 -03:00 committed by Richard Purdie
parent 8de7978284
commit 5dd5fd0d56

View File

@ -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