From: Radu Moisan <radu.moisan@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: systemd: /run directory not created
Date: Fri, 25 Jan 2013 10:28:44 +0200 [thread overview]
Message-ID: <5102423C.4010408@intel.com> (raw)
In-Reply-To: <CAJTo0LZ2ox=zgiAHS=DnbF9cv+vofjZpbqy8i0KEa6t1gezJPw@mail.gmail.com>
On 01/24/2013 04:52 PM, Burton, Ross wrote:
> On 24 January 2013 13:03, Radu Moisan <radu.moisan@intel.com> wrote:
>> ok, thanks Enrico, this clears the picture for me.
>> Well then it looks like Jack's problems is coming from some other place.
> No - /run needs to exist for the mount to happen, and there isn't a
> /run in the filesystem. Whatever creates the root filesystem
> structure should also create /run I guess.
I agree, but what I meant was that my initial assumptions were wrong
with concern to Jack's problem. I run it on qemu and /run is there. His
problem related to /run creation while I was thinking about mounting issue.
Radu
next prev parent reply other threads:[~2013-01-25 8:37 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 [this message]
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=5102423C.4010408@intel.com \
--to=radu.moisan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.