From: Juan Perez-Sanchez <lithoxs@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: An "ELKS BusyBox" is in progress; 24.5% size savings so far!
Date: Tue, 28 Feb 2012 15:28:22 -0600 [thread overview]
Message-ID: <CAD6VGuZRnedugzZEE6RvQ6WE_dpJ3kdgHJ=JAXiJYQ4FDJZTGA@mail.gmail.com> (raw)
In-Reply-To: <4F41E046.6000208@jodybruchon.com>
On 2/19/12, Jody Bruchon <jody@jodybruchon.com> wrote:
> 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
> -----
In the source bcc development package, under the directory "tests",
there is the source of
a "ft" (file tool) command. The last version includes 15 file
utilities such as cat, cp mkdir, etc.
apparently not as basic as their elkscmd counterparts. It might be worth to copy
the file to elkscmd.
prev parent reply other threads:[~2012-02-28 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 5:55 An "ELKS BusyBox" is in progress; 24.5% size savings so far! Jody Bruchon
[not found] ` <CAMKR1ysa2wnb=kPK3DMpqfT3i87exO5SKZDrTs-VpGOv1Ugy_Q@mail.gmail.com>
2012-02-22 14:42 ` Jody Bruchon
2012-02-28 21:28 ` Juan Perez-Sanchez [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='CAD6VGuZRnedugzZEE6RvQ6WE_dpJ3kdgHJ=JAXiJYQ4FDJZTGA@mail.gmail.com' \
--to=lithoxs@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).