From: Jonathan Liu <net147@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] base-files: add /run to dirs755 for systemd
Date: Sun, 19 May 2013 23:25:52 +1000 [thread overview]
Message-ID: <5198D2E0.1050705@gmail.com> (raw)
In-Reply-To: <CAJTo0Las4vi+firZWYxq22uSrGUmeZTG8eQSX+cADXLFiV3D+w@mail.gmail.com>
On 13/05/2013 8:53 PM, Burton, Ross wrote:
> On 13 May 2013 04:58, Jonathan Liu <net147@gmail.com> 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
prev parent reply other threads:[~2013-05-19 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 3:58 [PATCH] base-files: add /run to dirs755 for systemd Jonathan Liu
2013-05-13 10:53 ` Burton, Ross
2013-05-19 13:25 ` Jonathan Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5198D2E0.1050705@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox