public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: systemd: /run directory not created
Date: Thu, 24 Jan 2013 13:20:31 +0100	[thread overview]
Message-ID: <lyd2wug4c0.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <510124FE.6040901@intel.com> (Radu Moisan's message of "Thu, 24 Jan 2013 14:11:42 +0200")

Radu Moisan <radu.moisan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:

>>> 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)

yes; that's the best way.  Make /var/run a symlink pointing to /run.


> 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.

/run is part of systemd's api and mounted very early internally by
systemd.  This mountpoint must exist in the filesystem and it will
probably not work when it is symlink into /var/volatile which gets
mounted later.


Enrico



  parent reply	other threads:[~2013-01-24 12:35 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 [this message]
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=lyd2wug4c0.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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