On 13/05/2013 8:53 PM, Burton, Ross wrote:
On 13 May 2013 04:58, Jonathan Liu <[email protected]> wrote:
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 is a genuine bug, but I'm not convinced it is the whole fix.
What about non-systemd images? /run is meant to be a tmpfs, which is
why udev installs a volatile link from /run to /var/run. If we create
a directory in sysvinit cases, we'll also need to mount a tmpfs on it.
The FHS 3 draft specification actually ratifies /run[1] so we could
take this advantage to start cleaning up our volatile layout in /var.
Start by always creating /run in base-files, and always mounting it as
tmpfs in fstab for the non-systemd case. Then we can symlink /var/run
to /run, /var/lock to /run/lock, and so on.
I have submitted a more complete patch for your review.
Ross
[1] http://www.linuxbase.org/betaspecs/fhs/fhs.html#runRuntimeVariableData
Regards,
Jonathan
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
