[OE-core] [Draft design][RFC] Running postinst at rootfs generation time
richard.purdie at linuxfoundation.org
Tue Jun 28 15:15:43 CEST 2011
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 :/.
More information about the Openembedded-core