On 7/5/11 5:06 AM, Hauser, Wolfgang (external) wrote: > To build a read-only image, we have to set up an extra layer where we > modified all packages they cause a runtime modification. > > Especially we have to cover some adduser/addgroup issues, modify the volatile > file handling for our needs, and for omap3 graphics the handling of the GLES > version. > A failed offline postinst causing a runtime configuration. So the image > generation log has to be checked for such failing scripts.
Just an FYI, with the new adduser/group code.. that should no longer be one of the contributing factors.. we can now add users and groups during recipe / rootfs construction. > Some of the packages (e.g. dropbear) are prepared for supporting read-only > filesystems. Most packages are not. > > The problem with the alphabetic order of the postinst scripts we managed by > renaming some of the packages to fit the needed order. An ugly solution, but > in case of missing python skills, the easiest. Ya, this one bothers me slightly... and I'm not really sure how to solve it... --Mark > Nice to see someone having the same needs we have to fit. > > Regards > Wolfgang Hauser > > -----Ursprüngliche Nachricht----- > Von: Tom Parkin [mailto:tom.par...@gmail.com] > Gesendet: Dienstag, 5. Juli 2011 10:42 > An: Patches and discussions about the oe-core layer > Cc: Hauser, Wolfgang (external) > Betreff: Re: [OE-core] [Draft design][RFC] Running postinst at rootfs > generation time > > I'm interested to read about this initiative as we've recently > stumbled over the issue of postinst scripts in trying to port our > build to OE. > > So far it seems the primary concern is about the boot-time impact of > postinst on the target. But for the use-cases I'm interested in, we > need to capture all install processes as a part of the build in order > to output a fully-provisioned read-only rootfs image (e.g. squashfs). > Our boxes don't typically modify their filesystems at runtime, other > than to take full updates (completely new rootfs images). > > I think the reduction, or even elimination, of target-run postinst > scripts would help a lot with the read-only rootfs case. > > Tom > > On 4 July 2011 01:23, Cui, Dexuan <dexuan....@intel.com> wrote: >> Hauser, Wolfgang (external) wrote: >>> Beside the discussed changes, the postinst scripts should be executed >>> in the dependency order. >>> At the time, the scripts are executed in alphabetic order, which >>> breaks the image generation if depended packages are not in >>> alphabetic order. >>> >>> e.g. busybox and busybox subpackages (busybox-mdev). >>> >>> Regards >>> Wolfgang Hauser >>> >> >> Thank all for the suggestions! >> I created a wiki page to summarize the mail threads: >> https://wiki.yoctoproject.org/wiki/Run_postinst_during_rootfs_generation >> >> Thanks, >> -- Dexuan >> >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> > > > _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
