The /run directory needs to exist when using systemd otherwise startup fails with the following error: systemd[1]: Failed to mount /run: No such file or directory
This affects directdisk and vmdk images but images using an initrd do not appear to be affected. Tested with sysvinit and systemd running core-image-minimal qemux86 under QEMU. Jonathan Liu (1): base-files: add /run directory from FHS 3 draft specification meta/recipes-core/base-files/base-files/fstab | 1 + meta/recipes-core/base-files/base-files_3.0.14.bb | 12 ++++++------ meta/recipes-core/initscripts/initscripts-1.0/volatiles | 7 +++---- meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +- meta/recipes-core/systemd/systemd/00-create-volatile.conf | 2 -- meta/recipes-core/systemd/systemd/var-run.conf | 4 ---- meta/recipes-core/systemd/systemd_199.bb | 5 +---- meta/recipes-core/udev/udev.inc | 6 +----- meta/recipes-core/udev/udev/init | 1 - meta/recipes-core/udev/udev/volatiles | 1 - meta/recipes-core/udev/udev_182.bb | 2 +- 11 files changed, 14 insertions(+), 29 deletions(-) delete mode 100644 meta/recipes-core/systemd/systemd/var-run.conf delete mode 100644 meta/recipes-core/udev/udev/volatiles -- 1.8.2.3 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
