Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] meta-systemd: Introduce a create-volatile to create tmp directories
Date: Sat, 15 Sep 2012 11:26:35 +0200	[thread overview]
Message-ID: <k31hk6$es6$1@ger.gmane.org> (raw)
In-Reply-To: <1347641974-4993-1-git-send-email-holger+oe@freyther.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 14-09-12 18:59, Holger Hans Peter Freyther schreef:
> From: Holger Hans Peter Freyther <zecke@selfish.org>
> 
> The base-files create symlinks from /var/{log,tmp,lock,cache,run} to the
> /var/volatile. The directories are created by sysv initscripts. Use the
> systemd-tmpfiles to create the directories. One needs to be careful with
> the naming of the file as systemd first collects all *.conf files, sorts
> them by name and is parsing them then. Make sure the new file is parsed
> before the systemd.conf.

I'm not sure this is the right place to fix it, I'd prefer a base files
bbappend and an fs-perms.txt for this. You know, like angstrom does :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQVEnLMkyGM64RGpERAnhuAJ9jXlRDx9WddJ1zMaByOElCh2dUPQCgqedT
E1bm2zqcw4woino/cCXtQfM=
=CAHE
-----END PGP SIGNATURE-----




  reply	other threads:[~2012-09-15  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 16:59 [PATCH] meta-systemd: Introduce a create-volatile to create tmp directories Holger Hans Peter Freyther
2012-09-15  9:26 ` Koen Kooi [this message]
2012-09-15 13:20   ` Holger Hans Peter Freyther
2013-01-22 15:02 ` Peter A. Bigot
     [not found]   ` <20130123195059.GG2634@xiaoyu.lan>
2013-01-23 20:44     ` Peter A. Bigot

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='k31hk6$es6$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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