From: Mike Looijmans <mike.looijmans@topic.nl>
To: yocto@yoctoproject.org
Subject: Re: I hate busybox!
Date: Thu, 17 Sep 2015 09:12:53 +0200 [thread overview]
Message-ID: <55FA67F5.2010301@topic.nl> (raw)
In-Reply-To: <F45FA12158354FC0BEDC44D9390F3A23@PAULD>
On 16-09-15 18:43, Paul D. DeRocco wrote:
>> From: Mike Looijmans
>>
>> "Embedded" in my world is not about RAM or disk size. It's about
>> building a device that has a set task in life, and nothing is as
>> important as that one task. Whether that's running on an i7
>> or an M3 is irrelevant.
>>
>> For a system to acquire and process sensor data, record your
>> favorite TV
>> shows, or guide a missile, there's no need for a full fledged
>> bash shell
>> interpreter. It just needs a bit of plumbing to get the
>> application up
>> and running, and that's about it.
>>
>> Busybox is for systems like that. For these systems, anything more is
>> overkill, and will waste resources and increase the boot time.
>
> If you've got a 1GB eSSD drive, because that's the smallest you can buy,
> having a 382MB image rather than a 346MB image isn't a waste of anything.
To me it looks like a waste of 36 MB that could have been used for storing
useful data.
For many projects, 36MB is more than I have for the whole root filesystem.
Usually I get between 8 and 32 MB for the whole system (bootloader, kernel,
rootfs and user data storage).
> How much boot time increase do you think you'll get from full-featured
> command line tools? I'd be surprised if it was noticeable to anyone.
My current boot time is about 4 seconds. The SD memory on this board reads at
roughly 20MB/s, so each MB that I need to read at boot will cost me 50ms
extra. That is most certainly measurable. The NAND flash reads at 10MB/s, so
that'll be 100ms per megabyte.
As I said before, you and I live in different worlds. From where I'm standing,
your system is the exception, not the rule.
prev parent reply other threads:[~2015-09-17 7:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 8:26 I hate busybox! Paul D. DeRocco
2015-09-15 8:45 ` Paul Eggleton
2015-09-15 10:44 ` Burton, Ross
2015-09-16 0:31 ` Paul D. DeRocco
2015-09-15 14:47 ` Trevor Woerner
2015-09-15 14:53 ` Trevor Woerner
2015-09-15 15:39 ` William Mills
2015-09-15 16:38 ` Romain Perier
2015-09-15 17:01 ` Bob Cochran
2015-09-15 18:22 ` Trevor Woerner
2015-09-15 19:30 ` Bob Cochran
2015-09-16 0:35 ` Paul D. DeRocco
2015-09-16 1:13 ` Khem Raj
2015-09-16 1:21 ` Paul D. DeRocco
2015-09-16 7:01 ` Mike Looijmans
2015-09-16 16:43 ` Paul D. DeRocco
2015-09-16 20:23 ` Khem Raj
2015-09-16 21:07 ` Paul D. DeRocco
2015-09-16 21:17 ` Khem Raj
2015-09-17 7:12 ` Mike Looijmans [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=55FA67F5.2010301@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=yocto@yoctoproject.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.