Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-systemd] base-files and systemd services
Date: Fri, 14 Sep 2012 11:03:52 -0500	[thread overview]
Message-ID: <50535568.2060407@windriver.com> (raw)
In-Reply-To: <20120914114711.GF22757@localhost>

On 9/14/12 6:47 AM, Holger Hans Peter Freyther wrote:
> On Fri, Sep 14, 2012 at 10:16:44AM +0200, Holger Hans Peter Freyther wrote:
>> Good Morning,
>>
>>
>> a.) Use a tempfiles.d/volatile.conf to create these directories?
>
> this does not work due the implementation of systemd-tmpfiles. It might
> or might not (depending on the hash of the dir to be created) create the
> /var/volatile/tmp dir before it creates /var/log/tmp/wtmp. I will have
> to patch the tmp.conf.
>
>> b.) Install initscripts in my systemd image?
>> c.) ???

I'd suggest two possible fixes, the first is somewhat "obvious" to me.  Fix the 
setup/initialization scripts to make sure /var/volatile is setup/mounted before 
systemd starts doing it's stuff....

But the alternative (if that is not reasonable or possible), create a custom 
"fs-perms.txt" to describe a functional filesystem layout for a systemd based 
configuration.  (This can be carried in the systemd layer.)

--Mark

> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




      reply	other threads:[~2012-09-14 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  8:16 [meta-systemd] base-files and systemd services Holger Hans Peter Freyther
2012-09-14 11:47 ` Holger Hans Peter Freyther
2012-09-14 16:03   ` Mark Hatle [this message]

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=50535568.2060407@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-devel@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