All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: systemd: /run directory not created
Date: Thu, 14 Feb 2013 15:57:05 +0000	[thread overview]
Message-ID: <511D0951.4070406@communistcode.co.uk> (raw)
In-Reply-To: <511D0669.6020903@communistcode.co.uk>

On 14/02/13 15:44, Jack Mitchell wrote:
> On 14/02/13 15:31, Burton, Ross wrote:
>> On 14 February 2013 14:31, Jack Mitchell <ml@communistcode.co.uk> wrote:
>>> Did this ever go anywhere? I have just tried again today with 
>>> exactly the
>>> same result, all I did was change the DISTRO_FEATURES_INITMAN to 
>>> systemd.
>> Odd, as I just built and booted a systemd image (core-image-sato, in
>> poky master), and it worked fine.
>>
>> Ross
>
> I have a custom distro definition that cuts a lot of features out. Can 
> you find out which package is supposed to create run and I can check 
> if it is pulled in properly on my setup?
>
> I think something must be assumed somewhere and I don't have the 
> features enabled to trigger it.
>

 From a quick look it seems as though volatiles in initscripts-1.0 
should create the run directory if it's not found. However the 
initscripts package doesn't get pulled in on my image at all, and I 
can't see an equivalent in the systemd package.



-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2013-02-14 16:13 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 [this message]
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=511D0951.4070406@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 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.