[oe] Is there a recipe for building and using busybox with libbusybox out there ?

Koen Kooi k.kooi at student.utwente.nl
Wed Jul 7 12:20:46 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07-07-10 14:01, Hauser, Wolfgang (external) wrote:
> As I am a little new in OE, where you suggest to add a post process command to remove
> the S98configure ?
> 
> In the image recipe ? In the busybox recipe ?

in the image recipe using something like:

ROOTFS_POSTPROCESS_COMMAND += " ; rm file"

regards,

Koen

> 
> Append to which command ?
> 
> Regards 
> Wolfgang Hauser
>   
> -----Ursprüngliche Nachricht-----
> Von: openembedded-devel-bounces at lists.openembedded.org [mailto:openembedded-devel-bounces at lists.openembedded.org] Im Auftrag von Koen Kooi
> Gesendet: Mittwoch, 7. Juli 2010 12:49
> An: openembedded-devel at lists.openembedded.org
> Betreff: Re: [oe] Is there a recipe for building and using busybox with libbusybox out there ?
> 
> On 07-07-10 12:26, Phil Blundell wrote:
>> On Wed, 2010-07-07 at 11:45 +0200, Hauser, Wolfgang (external) wrote:
>>> I want to use busybox with the applet binaries linked against libbusybox
>>> in our system.
>>> We need a wide range of applets at the same time, so I suppose it will
>>> save overall needed memory space.
> 
>> What's the advantage of this?  I would have thought it would give you a
>> larger memory footprint rather than a smaller one.  I guess I must be
>> missing something.
> 
>>> Also I want to prevent the system from updating alternatives while the
>>> first boot. We have to provide a read only root file system.
> 
>> Yeah, this is a long-standing piece of OE suckage.  We should fix the
>> alternative selection to work at image construction time.
> 
> OE already does that. But what it does after that is flag everything as
> 'unpacked' to have opkg rerun all postinsts at boot *again*. If OE
> didn't run u-a at image time we wouldn't be able to use sysvinit for
> example.
> If you only care about u-a, just add a post process command to remove
> the S98configure from the rootfs and opkg won't run.
> 
> In the long run a way to control this behaviour and optionally hook into
> qemu or even targets over network to run them at image time. Having to
> run a first boot, remove ssl keys and repackage everything is getting a
> bit tedious.
> 
> regards,
> 
> Koen

_______________________________________________
Openembedded-devel mailing list
Openembedded-devel at lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMNHEeMkyGM64RGpERAlb/AJ94spQyrbNfaJRTFlrNT0UG4h9lfgCfWDcZ
/NBxZJl6VUWy+XT34c75Mp8=
=V5gc
-----END PGP SIGNATURE-----





More information about the Openembedded-devel mailing list