From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Is there a recipe for building and using busybox with libbusybox out there ?
Date: Wed, 07 Jul 2010 11:26:29 +0100 [thread overview]
Message-ID: <1278498389.2345.1744.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <0B51A1E7C61D114DAE6FC10B0FD0ABA501819C15@deimsg40.de.net.world>
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.
p.
next prev parent reply other threads:[~2010-07-07 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 9:45 Is there a recipe for building and using busybox with libbusybox out there ? Hauser, Wolfgang (external)
2010-07-07 9:52 ` Roman I Khimov
2010-07-07 10:38 ` [PATCH] busybox: add suport for FEATURE_INDIVIDUAL setup Roman I Khimov
2010-07-12 5:32 ` Roman I Khimov
2010-07-12 7:41 ` Hauser, Wolfgang (external)
2010-07-12 18:34 ` Khem Raj
2010-07-12 19:21 ` Roman I Khimov
2010-07-12 19:41 ` Khem Raj
2010-07-07 12:09 ` Is there a recipe for building and using busybox with libbusybox out there ? Hauser, Wolfgang (external)
2010-07-07 12:21 ` Roman I Khimov
2010-07-07 10:26 ` Phil Blundell [this message]
2010-07-07 10:48 ` Koen Kooi
2010-07-07 12:01 ` Hauser, Wolfgang (external)
2010-07-07 12:20 ` Koen Kooi
2010-07-07 11:34 ` Hauser, Wolfgang (external)
2010-07-07 11:58 ` Phil Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1278498389.2345.1744.camel@mill.internal.reciva.com \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox