From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: systemd: /run directory not created
Date: Mon, 15 Apr 2013 13:58:52 +0100 [thread overview]
Message-ID: <516BF98C.2080603@communistcode.co.uk> (raw)
In-Reply-To: <512785CE.5020508@communistcode.co.uk>
Ok, I have just come back to trying out the new systemd implementation,
and this bug still exists.
Exactly the same error as before:
[ 2.390730] systemd[1]: Failed to mount /run: No such file or directory
Can we shed any light on why this directory is failing to be created and
what can be done to fix it. Having looked in my final target filesystem
there are no links to the volatiles in /var/voltatile/* to /*, should
there be? The base-files packages looks like it should do it but
obviously something is going wrong.
for d in ${volatiles}; do
ln -sf volatile/$d ${D}${localstatedir}/$d
done
Cheers,
Jack.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-04-15 13:16 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
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 [this message]
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=516BF98C.2080603@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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