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: Thu, 24 Jan 2013 14:11:42 +0200 [thread overview]
Message-ID: <510124FE.6040901@intel.com> (raw)
In-Reply-To: <CAJTo0LZfGGSdQwKMshr8PNUVZfk4Nwhr67-9iFbGw2=V=YqN8g@mail.gmail.com>
On 01/24/2013 02:01 PM, Burton, Ross wrote:
> On 24 January 2013 09:46, Radu Moisan <radu.moisan@intel.com> wrote:
>> 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.
> I wonder how my images booted... initscripts is sysvinit specific,
> the systemd startup should handle this somehow.
>
> (insert standard argument that we should adopt /run across all init systems)
>
This is exactly what I was looking for. /run shouldn't be there, yet
somehow it is. I was looking into how/where systemd is creating /run but
no lead for now.
Radu
next prev parent reply other threads:[~2013-01-24 12:20 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 [this message]
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=510124FE.6040901@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.