From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: An "ELKS BusyBox" is in progress; 24.5% size savings so far!
Date: Mon, 20 Feb 2012 00:55:18 -0500 [thread overview]
Message-ID: <4F41E046.6000208@jodybruchon.com> (raw)
I'm pleased to announce my development of a sub-project I am coining
"BusyELKS" which serves the same purpose for ELKS that BusyBox does for
larger Linux systems. I have spent most of my evening combining the
files under elkscmd/sh_utils into a unified binary that executes the
requested command based on its invocation name, and the savings just for
sh_utils is awesome! Ignoring the "uname" tool which currently does not
compile, the binary size total drops from 61920 to 46732, a whopping
15188-byte (24.5%) drop in size! See for yourself:
648 ../sh_utils/basename
7232 ../sh_utils/date
536 ../sh_utils/dirname
360 ../sh_utils/echo
212 ../sh_utils/false
536 ../sh_utils/printenv
1836 ../sh_utils/pwd
212 ../sh_utils/true
3788 ../sh_utils/which
1896 ../sh_utils/whoami
328 ../sh_utils/yes
1896 ../sh_utils/logname
7256 ../sh_utils/tr
8320 ../sh_utils/xargs
7900 ../sh_utils/mesg
16148 ../sh_utils/stty
2816 ../sh_utils/test
-----
61920 total
-rwxr-xr-x 1 root root 46732 Feb 20 00:40 busyelks*
My preliminary binary isn't ready to be put to use yet; I still have
that pesky 64K barrier that I will have to fight with eventually, and
there are many more optimizations I haven't performed, but it's a start!
Even if I can only unify the utilities by category, we can look forward
to significant space savings from this effort. Once I've got the
structure cleaned up a bit and some disparities merged together, I'll
commit BusyELKS to Git. Stay tuned.
Jody Bruchon
next reply other threads:[~2012-02-20 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 5:55 Jody Bruchon [this message]
[not found] ` <CAMKR1ysa2wnb=kPK3DMpqfT3i87exO5SKZDrTs-VpGOv1Ugy_Q@mail.gmail.com>
2012-02-22 14:42 ` An "ELKS BusyBox" is in progress; 24.5% size savings so far! Jody Bruchon
2012-02-28 21:28 ` Juan Perez-Sanchez
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=4F41E046.6000208@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.