Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/1] busybox: update to 1.19.3
Date: Wed, 23 Nov 2011 09:59:07 +0100	[thread overview]
Message-ID: <20111123085906.GA16705@ad.chargestorm.se> (raw)
In-Reply-To: <4ECC07D8.2070104@linux.intel.com>

* Saul Wold <sgw@linux.intel.com> [111122 21:36]:
> On 11/22/2011 06:34 AM, Anders Darander wrote:
> > This updates busybox to the latest stable, 1.19.3.

> > Among other things, there should be rudimentary support in syslogd for
> > systemd, by enabling CONFIG_FEATURE_SYSTEMD.

> How much size does this add to busybox by having it enabled by default?

Enabling FEATURE_SYSTEMD in busybox costs 192 bytes in my tests in
qemux86.

> Is it possible to conditional add a config fragment if systemd is 
> enabled ad the DISTRO/IMAGE_FEATURE level?

> More info is required.

> > It has been tested and verified on qemux86 and on our local arm-based system.

> > However, the patch busybox-udhcpc-no_deconfig.patch has been modified to
> > apply, but hasn't really been tested. As we're currently mostly running static
> > configurations, we've only verified that udhcpc works to the extent that we
> > get the network up and running, not how it behaves during dhcp renewal.
> > Thus I'm starting this as an RFC.

> > Changes:
> > v2: * Checked the new defconfig (removed settings implying CFLAGS and
> >      ARCH). The new defconfig should be as close as possible to the old one,
> >      with the exception of some new utils/options.
> Can you clearly enumerate what new utils and options and what their size 
> impact on the busybox image is.

Apart from the FEATURE_SYSTEMD discussed above, these are the other new
options that I kept the new busybox default on (i.e. these are enabled,
while I turned of quite a few other options that automatically got
enabled). All costs are evaluted using qemux86, and the busybox binary
size is checked in the packages-split/busybox/bin directory.

I don't mind disabling any of these feature in a v3, if
desired/requested. Anyway, I'm running a completely custom config for my
normal uses...

FEATURE_RTMINMAX, support RTMIN[+n] RTMAX[-n] signals, claimed to cost
~250 bytes

FEATURE_REVERSE_SEARCH claimed to cost ~0.5k

FEATURE_SKIP_ROOTFS ignore rootfs entry in mount table (tools like df
etc will ignore it).

FEATURE_AR_CREATE, enable ar to create files, ~2.5k

FEATURE_SEAMLESS_XZ enable xz compression in tar, no measured cost.

XZ and UNXZ, enable xz compression, 8k

FGCONSOLE, print active console number, 128 bytes

FEATURE_LOADFONT_PSF2, FEATURE_LOADFONT_RAW, cost 576 bytes

FEATURE_VI_ASK_TERMINAL, last resort to find terminal size, 352 bytes

BLOCKDEV, perform some ioctls with block devices, cost 480 bytes

FDISK_SUPPORT_LARGE_DISKS, is disabled, it no longer wants to play with
LFS (both were enabled previously).

FEATURE_MOUNT_LOOP_CREATE, create new loopback devices if needed,
couldn't see any cost

FEATURE_WGET_TIMEOUT, no visible cost

FEATURE_SH_HISTFILESIZE, use $HISTFILESIZE (still max limited by
config), no visible cost

FEATURE_SYSLOGD_CFG, support syslog.conf, no visible cost

FEATURE_SYSLOGD_READ_BUFFER_SIZE, defines the size of the read buffer,
not measured

FEATURE_KLOGD_KLOGCTL, let klogd use the klogctl() interface, no visible
cost

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB



  parent reply	other threads:[~2011-11-23  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 14:34 [PATCH v2 0/1] busybox: update to 1.19.3 Anders Darander
2011-11-22 14:34 ` [PATCH v2 1/1] " Anders Darander
2011-11-22 20:36 ` [PATCH v2 0/1] " Saul Wold
2011-11-22 20:47   ` Anders Darander
2011-11-23  8:59   ` Anders Darander [this message]
2011-11-29  5:47     ` Saul Wold
2011-11-29  7:04       ` Anders Darander
2011-11-29  7:54         ` Phil Blundell
2011-11-29  8:13         ` Saul Wold
2011-11-29  8:29           ` Anders Darander
2011-11-23 10:38   ` Otavio Salvador
2011-11-23 10:42     ` Anders Darander

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=20111123085906.GA16705@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --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