Re: [Draft design][RFC] Running postinst at rootfs generation time

From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [Draft design][RFC] Running postinst at rootfs generation time
Date: Tue, 28 Jun 2011 09:44:07 -0500	[thread overview]
Message-ID: <4E09E8B7.1070901@windriver.com> (raw)
In-Reply-To: <1309266943.20015.290.camel@rex>

On 6/28/11 8:15 AM, Richard Purdie wrote:
> On Mon, 2011-06-27 at 23:11 -0500, Mark Hatle wrote:
>> On 6/27/11 9:09 PM, Cui, Dexuan wrote:
>>> Hi all, below is an initial investigation about the task and we'll continue to further look into it.
>>>
>>> In poky we have 2 types of postinst scripts:  one (type-1) can be (and has already been) run at rootfs generation time and the other (type-2) has to be delayed to the first-boot of target device. Type-2 makes target device's first-boot slow and it would be great if we can fix it and convert it to type-1.
>>>
>>> We can instrument a first-boot with minimal/sato first to see which postinstalls take the most time and then prioritise those ones to fix.
>>>
>>> I figurerd out a list of 33 recipes in total(recipes with the same name but with different versions are counted once) we possibly need to fix.
>>> For the recipes, we need try to find recipe-specific ways(use appropriately modified native utilities to generate caches, files, etc as necessary on the target filesystem).
>>>
>>
>> ...
>>
>>> 1 recipe: prelink: we could propablly fix it, but I'm not sure yet.
>>> meta/recipes-devtools/prelink/prelink_git.bb
>>
>> There is nothing to do for the prelinker.  The "image-prelink.bbclass" handles
>> everything needed to prelink during image creation.  The script is only there
>> for on-target field upgrades.  So you can remove this from your list.
> 
> Mark, are you 100% sure about this?
> 
> It looks like if we install prelink into an image it adds a post install
> which runs "prelink -a" on the target device at first boot.
> 
> This would happen regardless of whether the cross prelinker did or did
> not prelink the image :/.

That is certainly not the intention of this code.  If it does, it should be a
fairly quick bug to fix -- and improve boot-time.  (Of course, this only should
be skipped if we've done image-prelink.bbclass.)

I'll attempt to look into this shortly....

--Mark

> Cheers,
> 
> Richard
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core