From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH RFC 0/2] eliminate (almost all of) busybox for GNUish images
Date: Wed, 10 Oct 2012 09:43:53 +0200 [thread overview]
Message-ID: <50752739.4000401@linaro.org> (raw)
In-Reply-To: <1349821315-18006-1-git-send-email-andy.ross@windriver.com>
W dniu 10.10.2012 00:21, Andy Ross pisze:
> We've been attempting to build an image that is busybox-free.
> Unfortunately there are a handful of busybox applets which are used in
> existing functionality (mostly various initscripts) and for which
> oe-core has no packaged replacements:
>
> + /usr/bin/run-parts - part of upstream debianutils, unpackaged.
>
> + /sbin/start-stop-daemon - part of upstream dpkg, built by oe-core
> recipe but unpackaged.
>
> + /sbin/if{up,down} - upstream ifupdown, but busybox version is AFAICT
> quite divergent.
>
> These are all tiny, and probably not worth having in distinct binaries.
> The attached patch breaks out a separate "busybox-oe-min" package that
> can be installed in images that don't need or want the full busybox
> binary. It comes to 41kb on my x86 build.
>
> Note that busybox is still pulled in by packagegroup-core-boot, so none of
> the existing images will use this package without modification.
In OE Classic we had task-proper-tools which replaced busybox and gave
working images.
prev parent reply other threads:[~2012-10-10 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 22:21 [PATCH RFC 0/2] eliminate (almost all of) busybox for GNUish images Andy Ross
2012-10-09 22:21 ` [PATCH 1/2] busybox: Factor out defconfig and binary name Andy Ross
2012-10-09 22:21 ` [PATCH 2/2] busybox-oe-min: add package for minimal non-busybox systems Andy Ross
2012-10-10 7:43 ` Marcin Juszkiewicz [this message]
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=50752739.4000401@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@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