From: "\"Andreas Müller\"" <Schnitzeltony@gmx.de>
To: openembedded-core@lists.openembedded.org, schnitzeltony@gmx.de
Subject: Re: How to overlay files/fs-perms.txt?
Date: Tue, 11 Oct 2011 13:23:06 +0200 [thread overview]
Message-ID: <20111011112306.15960@gmx.net> (raw)
In-Reply-To: <DDA1B8C5-0867-406F-BB88-0D33B7501900@dominion.thruhere.net>
See
I guess it is found in line 553 of oe-core package.bbclass
fs_perms_tables = bb.data.getVar('FILESYSTEM_PERMS_TABLES', d, True)
Andreas
-------- Original-Nachricht --------
> Datum: Tue, 11 Oct 2011 12:42:01 +0200
> Von: Koen Kooi <koen@dominion.thruhere.net>
> An: Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
> Betreff: [OE-core] How to overlay files/fs-perms.txt?
> Hi,
>
> In angstrom we have base-files overlayed to clean out /var and
> files/fs-perms.txt is getting in the way of that:
>
> koen@dominion:/OE/tentacle/sources/openembedded-core/meta$ grep localstate
> files/fs-perms.txt
> ${localstatedir}/cache link volatile/cache
> ${localstatedir}/run link volatile/run
> ${localstatedir}/log link volatile/log
> ${localstatedir}/lock link volatile/lock
> ${localstatedir}/tmp link volatile/tmp
>
> In angstrom those aren't symlinks anymore, but tmpfs bind mounts managed
> by systemd.
>
> So, how doI overlay that file in this oe-core layer universe?
>
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
next prev parent reply other threads:[~2011-10-11 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 10:42 How to overlay files/fs-perms.txt? Koen Kooi
2011-10-11 10:59 ` Richard Purdie
2011-10-11 11:23 ` "Andreas Müller" [this message]
2011-10-11 19:03 ` Mark Hatle
2011-10-11 19:12 ` Mark Hatle
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=20111011112306.15960@gmx.net \
--to=schnitzeltony@gmx.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 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.