Should BusyBox and uClibc also make a "flag version" likeEmbedded Linux?
Denys Vlasenko
vda.linux at googlemail.com
Sat Nov 6 00:30:08 UTC 2010
On Sat, Nov 6, 2010 at 12:06 AM, Cathey, Jim <jcathey at ciena.com> wrote:
> consider updating. But if BB v20 is notably bigger
> than BB v2, as configured, that could be a problem.
>
> Especially if the toaster were quite resource-constrained.
> And spending more ROM bytes on infrastructure like BB is
> usually much less attractive than spending them on direct
> features.
Let's see. Here is 1.00 defconfig versus 1.17.3 with the equivalent config
(both .configs are attached):
text data bss dec hex filename
296235 4212 40560 341007 5340f busybox-1.00/busybox
305633 3041 8944 317618 4d8b2 busybox-1.17.3/busybox
As you see, a bit more code, a lot less data, with overall decrease in size.
Worst size offenders, BTW, aren't in 1.00 defconfig - try enabling dpkg.
It has 276656 (!!!) bytes of bss in common variables:
# nm --size-sort dpkg.o | tail -3
0000000000010000 C status_hashtable
00000000000138c0 C package_hashtable
000000000001fff0 C name_hashtable
> 'Stale' software is a fact of life in embedded world.
> We prefer to pronounce it 'stable', however!
I wasn't implying you are using staBle software for bad reasons :D
--
vda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config-1.00.bz2
Type: application/x-bzip2
Size: 2178 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/uclibc/attachments/20101106/88dd7cb9/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config-1.17.3.bz2
Type: application/x-bzip2
Size: 5273 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/uclibc/attachments/20101106/88dd7cb9/attachment-0003.bin>
More information about the uClibc
mailing list