busybox: update to 1.19.3

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.

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.

* Added one patch from upstream, to safeguard the use of CBAUD termios_init().
* The other upstream patch from http://busybox.net/downloads/fixes-1.19.3/
do only affect comments, thus I'm not adding it.

The following changes since commit dd2fdf9f5a3923c37e4ea2e46e347bb0657c2f5b:

   gcc-4.6: Fix gcc ICE on qt4-x11-free/armv7-a (2011-11-21 16:55:01 +0000)

are available in the git repository at:
git://github.com/darander/oe-core busybox-systemd
https://github.com/darander/oe-core/tree/busybox-systemd

Anders Darander (1):

   busybox: update to 1.19.3

  .../B921600.patch                                  |    0
  .../busybox-1.19.3/busybox-1.19.3-getty.patch      |   17 ++
  .../busybox-appletlib-dependency.patch             |    0
  .../busybox-udhcpc-no_deconfig.patch               |   66 +++--
  .../{busybox-1.18.5 =>  busybox-1.19.3}/defconfig   |  265 +++++++++++++-------
  .../get_header_tar.patch                           |    0
  .../run-parts.in.usr-bin.patch                     |   16 +-
  .../udhcpc-fix-nfsroot.patch                       |    0
  .../udhcpscript.patch                              |    0
  .../{busybox_1.18.5.bb =>  busybox_1.19.3.bb}       |    7 +-
  10 files changed, 245 insertions(+), 126 deletions(-)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/B921600.patch (100%)
  create mode 100644 meta/recipes-core/busybox/busybox-1.19.3/busybox-1.19.3-getty.patch
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/busybox-appletlib-dependency.patch (100%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/busybox-udhcpc-no_deconfig.patch (62%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/defconfig (89%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/get_header_tar.patch (100%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/run-parts.in.usr-bin.patch (64%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/udhcpc-fix-nfsroot.patch (100%)
  rename meta/recipes-core/busybox/{busybox-1.18.5 =>  busybox-1.19.3}/udhcpscript.patch (100%)

rename meta/recipes-core/busybox/{busybox_1.18.5.bb => busybox_1.19.3.bb} (82%)

Quoted 5 lines · Anders Darander

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? Is it possible to conditional add a config fragment if systemd is enabled ad the DISTRO/IMAGE_FEATURE level?

More info is required.

Quoted 8 lines

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.

Quoted 4 lines

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.

Quoted 4 lines · Anders Darander

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?

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

More info is required.

Quoted 7 lines

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.

Quoted 4 lines

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.

Quoted 7 lines · Saul Wold

Quoted 4 lines · Anders Darander

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.

Quoted 13 lines

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

More info is required.

Quoted 7 lines

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.

Quoted 6 lines

Quoted 4 lines

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

Quoted 8 lines · Anders Darander

Quoted 7 lines · Saul Wold

Quoted 4 lines · Anders Darander

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?

Quoted 7 lines

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

Quoted 4 lines

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

More info is required.

Quoted 6 lines

Quoted 6 lines

Quoted 4 lines

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.

Quoted 9 lines

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...

Quoted 2 lines

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

I can see these being useful

Quoted 1 line

FEATURE_REVERSE_SEARCH claimed to cost ~0.5k

Why is this needed?

Quoted 5 lines

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

This is the one and the ar create above that sticks out, are these needed in the general case or just vfor your config?

Quoted 3 lines

FGCONSOLE, print active console number, 128 bytes

FEATURE_LOADFONT_PSF2, FEATURE_LOADFONT_RAW, cost 576 bytes

Seems resonable, but why did we not need this before, what changed?

Quoted 1 line

FEATURE_VI_ASK_TERMINAL, last resort to find terminal size, 352 bytes

Not sure about this and the FGCONSOLE above.

Quoted 1 line

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

Again is this useful in the general case?

Any more comment on this one? Otavio replied earlier that if it was a small cost, he would prefer to have it on by default. Otherwise, any suggestions for DISTRO/IMAGE_FEATURE?

Quoted 12 lines · Saul Wold

Quoted 11 lines · Anders Darander

Quoted 7 lines · Saul Wold

Quoted 4 lines · Anders Darander

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.

Quoted 4 lines

Quoted 4 lines

Quoted 4 lines

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

More info is required.

Any more comment on this one? Otavio replied earlier that if it was a small cost, he would prefer to have it on by default. Otherwise, any suggestions for DISTRO/IMAGE_FEATURE?

Quoted 6 lines

Quoted 6 lines

Quoted 6 lines

Quoted 4 lines

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.

I'll remove all features that you didn't OK (see below), unless we get some more replies/wishes in the next day. (Thus I plan to send a v3 this week, if times allow it).

Just to clarify it once more, the choice of which new features to enable was done by trying to judge if they were reasonable, or seemed helpfull/usefull enough. I'm not normally running with the defconfig (apart from testing this patch), I'm using a heavily customized and often minimized defconfig.

Quoted 10 lines

Quoted 9 lines

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...

Quoted 8 lines

Quoted 2 lines

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

I can see these being useful

Quoted 1 line

FEATURE_REVERSE_SEARCH claimed to cost ~0.5k

Why is this needed?

Not needed, just nice to have. But I'll remove it in v3.

Quoted 8 lines

Quoted 5 lines

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

This is the one and the ar create above that sticks out, are these needed in the general case or just vfor your config?

Shouldn't be needed. I just left it enabled as all other FEATURE_SEAMLESS's was enabled. I'll disable these two in v3.

Quoted 1 line

Quoted 1 line

FGCONSOLE, print active console number, 128 bytes

Quoted 3 lines

Quoted 1 line

FEATURE_LOADFONT_PSF2, FEATURE_LOADFONT_RAW, cost 576 bytes

Seems resonable, but why did we not need this before, what changed?

Not really sure what the change is (normally I'm only working on headless systems, thus no need for fonts). The two FEATURE_LOADFONT_* options were not available in the old defconfig. I'll leave these two in v3, as you thought the seemd reasonable.

Quoted 3 lines

Quoted 1 line

FEATURE_VI_ASK_TERMINAL, last resort to find terminal size, 352 bytes

Not sure about this and the FGCONSOLE above.

Sure, I'll remove these two.

Quoted 3 lines

Quoted 1 line

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

Again is this useful in the general case?

Same as previously, an arbitrary choice. I'll remove it in v3.

Quoted 18 lines · Anders Darander

Quoted 17 lines · Saul Wold

Quoted 16 lines · Anders Darander

Quoted 7 lines · Saul Wold

Quoted 4 lines · Anders Darander

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.

Quoted 4 lines

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

More info is required.

Quoted 3 lines

Any more comment on this one? Otavio replied earlier that if it was a small cost, he would prefer to have it on by default. Otherwise, any suggestions for DISTRO/IMAGE_FEATURE?

Sorry for not being clear on this on, yes to the SYSTEMD change, it's small enough and something we are considering. As Phil points out in the follow-up to this, most are using custom defconfig's that we should just go ahead and enable this for future flexibility.

Quoted 13 lines

Quoted 13 lines

Quoted 11 lines

Quoted 6 lines

Quoted 4 lines

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.

FGCONSOLE, print active console number, 128 bytes

FEATURE_LOADFONT_PSF2, FEATURE_LOADFONT_RAW, cost 576 bytes

Seems resonable, but why did we not need this before, what changed?

Quoted 4 lines

Not really sure what the change is (normally I'm only working on headless systems, thus no need for fonts). The two FEATURE_LOADFONT_* options were not available in the old defconfig. I'll leave these two in v3, as you thought the seemd reasonable.

For minimal, it's good to assume headless, then we should not need the LOADFONT. I thought it was needed for headless as well.

Quoted 6 lines · Anders Darander

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?

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

On Tue, Nov 22, 2011 at 18:36, Saul Wold <[email protected]> wrote:

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? Is it possible to conditional add a config fragment if systemd is enabled ad the DISTRO/IMAGE_FEATURE level?

If it is small it would be nice to have it enabled.