From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: How to overlay files/fs-perms.txt?
Date: Tue, 11 Oct 2011 11:59:45 +0100 [thread overview]
Message-ID: <1318330793.23801.88.camel@ted> (raw)
In-Reply-To: <DDA1B8C5-0867-406F-BB88-0D33B7501900@dominion.thruhere.net>
On Tue, 2011-10-11 at 12:42 +0200, Koen Kooi wrote:
> 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?
To quote package.bbclass:
# Return a list of configuration files based on either the default
# files/fs-perms.txt or the contents of FILESYSTEM_PERMS_TABLES
# paths are resolved via BBPATH
def get_fs_perms_list(d):
str = ""
fs_perms_tables = bb.data.getVar('FILESYSTEM_PERMS_TABLES', d, True)
if not fs_perms_tables:
fs_perms_tables = 'files/fs-perms.txt'
for conf_file in fs_perms_tables.split():
str += " %s" % bb.which(bb.data.getVar('BBPATH', d, True), conf_file)
return str
so it looks for a "files/fs-perms.txt" in BBPATH...
Cheers,
Richard
next prev parent reply other threads:[~2011-10-11 11:05 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 [this message]
2011-10-11 11:23 ` "Andreas Müller"
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=1318330793.23801.88.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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