From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: systemd: /run directory not created
Date: Thu, 24 Jan 2013 11:46:28 +0200 [thread overview]
Message-ID: <510102F4.70108@intel.com> (raw)
In-Reply-To: <50FFFF81.8010203@communistcode.co.uk>
On 01/23/2013 05:19 PM, Jack Mitchell wrote:
> When I attempt to boot a systemd enabled image I get an error stating
> that the run directory could not be mounted as it doesn't exist. I
> checked the target rootfs and there isn't a /run directory. What is
> responsible for creating this and why is it not doing it's job?
>
> [ 2.631549] systemd[1]: Failed to mount /run: No such file or directory
>
> Possibly of interest is that I am running a custom distro with
> manually specified DISTRO_FEATURES.
>
Possibly because /run was a link created by the initscripts which are
now disabled when systemd is the init manager. I'll look into this and
update 00-create-volatile.conf so that systemd will handle the link
creation in stead.
Radu
next prev parent reply other threads:[~2013-01-24 9:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 15:19 systemd: /run directory not created Jack Mitchell
2013-01-24 9:46 ` Radu Moisan [this message]
2013-01-24 12:01 ` Burton, Ross
2013-01-24 12:11 ` Radu Moisan
2013-01-24 12:11 ` Burton, Ross
2013-01-24 12:20 ` Enrico Scholz
2013-01-24 12:34 ` Radu Moisan
2013-01-24 12:53 ` Enrico Scholz
2013-01-24 13:03 ` Radu Moisan
2013-01-24 14:52 ` Burton, Ross
2013-01-25 8:28 ` Radu Moisan
2013-02-14 14:31 ` Jack Mitchell
2013-02-14 15:31 ` Burton, Ross
2013-02-14 15:44 ` Jack Mitchell
2013-02-14 15:57 ` Jack Mitchell
2013-02-14 20:23 ` Jack Mitchell
2013-02-21 22:27 ` Khem Raj
2013-02-22 9:22 ` Jack Mitchell
2013-02-22 14:15 ` Jack Mitchell
2013-02-22 14:50 ` Jack Mitchell
2013-04-15 12:58 ` Jack Mitchell
2013-04-15 13:10 ` Martin Jansa
2013-04-15 13:45 ` Jack Mitchell
2013-05-02 15:01 ` Jonathan Liu
2013-05-02 15:11 ` Jonathan Liu
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=510102F4.70108@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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