From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.windriver.com ([147.11.1.11]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1RDhh2-0007or-2f for openembedded-core@lists.openembedded.org; Tue, 11 Oct 2011 21:08:48 +0200 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p9BJ34Vr029236 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 11 Oct 2011 12:03:04 -0700 (PDT) Received: from Macintosh-5.local (172.25.36.226) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 11 Oct 2011 12:03:04 -0700 Message-ID: <4E9492E7.3070301@windriver.com> Date: Tue, 11 Oct 2011 14:03:03 -0500 From: Mark Hatle Organization: Wind River Systems User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: References: In-Reply-To: X-MIME-Autoconverted: from 8bit to quoted-printable by mail.windriver.com id p9BJ34Vr029236 Subject: Re: How to overlay files/fs-perms.txt? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2011 19:08:48 -0000 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable On 10/11/11 5:42 AM, Koen Kooi wrote: > Hi, >=20 > In angstrom we have base-files overlayed to clean out /var and files/fs= -perms.txt is getting in the way of that: >=20 > koen@dominion:/OE/tentacle/sources/openembedded-core/meta$ grep localst= ate files/fs-perms.txt=20 > ${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 >=20 > In angstrom those aren't symlinks anymore, but tmpfs bind mounts manage= d by systemd. >=20 > So, how doI overlay that file in this oe-core layer universe? This came up recently in regards to the Yocto documentation. Below is th= e snipped of conversation we had working on docs: >> I was discussing the fs-perms.txt file and the FILESYSTEM_PERMS_TABLES= variable >> with Paul. We got the point of user-scenarios. Paul said that he wou= ld >> recommend not setting the variable at all and just letting it default = to our >> fs-perms.txt file. At which point I asked why have the variable then?= Paul >> pointed me off to you at that point. >> > Reasons to set it. >=20 > You have custom files/directories in your layer and need to specify the= m via a > custom fs-perms.txt file. (More then one can be specified...) The fil= e (or > files) is "distribution specific". I.e. the distribution the developer= is > creating needs a consistent fs-perms.txt across the entire work product= . For > directories shared between packages, that use non-standard permissions,= owners > and/or groups, this is the way to synchronize the information. (Note, = it's > better to sync within the packages themselves, but that is not always p= ossible > to do.. primarily for the core package set.) >=20 >> So what I am trying to understand here is how a customer would go abou= t using >> their own fs-perms.txt file. Since we have the FILESYSTEM_PERMS_TABLE= S variable >> I presume someone can set it to point to an fs-perms.txt file of their= own. Can >> tell me how they do that with some answers to the following? >> > FILESYSTEM_PERMS_TABLES is by default "files/fs-perms.txt". One or mor= e file > can be added to this list. Each file listed will be scanned for via th= e BBPATH. > So you might end up with a "files/intel-perms.txt". This could be an = Intel > specific version of the file. Or set it to "files/fs-perms.txt > files/intel-perms.txt". In this case it will use BOTH the default and = the newly > mentioned intel-perms.txt. >=20 >> =B7 They create their own file following the syntax of the fs-= perms.txt >> file we supply and put it anywhere they want? > The path specified must be within the BBPATH. >=20 >> =B7 They edit the existing fs-perms.txt file we supply? (prob= ably not a >> good idea but thought I would ask) > It is best for them to supply their own file and include it in addition= to the > default file -- or completely replace the stock file. (editing the sto= ck > version makes long term maintenance more difficult if we need to make c= hanges to > it in the future.) >=20 >> =B7 Where do they set the FILESYSTEM_PERMS_TABLES variable? W= e set it in >> a place that they should not edit. > local.conf or any other place where bitbake variables can be set. >=20 >> =B7 Is the FILESYSTEM_PERMS-TABLES variable something that sho= uld just >> remain hidden? > I doubt it will be useful for general purpose stuff.. It's really for > distribution creators, more then distribution "users". Most of our (Yo= cto and > OE-Core) user base are "users". They use what we give them as a basis = for their > work, and then add to it. A distribution creator is someone who is goi= ng to > potentially chance the rules of the filesystem and where things belong = to suit > their (or their customers) needs. Hopefully this helps. --Mark > regards, >=20 > Koen > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core