BusyBox has been written with size-optimization and limited resources in mind.
It is also extremely modular so you can easily include or exclude commands (or
features) at compile time. This makes it easy to customize your embedded
-systems. To create a working system, just add /dev, a kernel, and an editor,
-such as nano, e3, or elvis-tiny. For a really minimal system, you can even use
-the busybox shell (not Bourne compatible, but very small and quite usable).
+systems. To create a working system, just add /dev, a shell, and a kernel. For
+a really minimal system, you can even use the busybox shell (not Bourne
+compatible, but very small and quite usable) and the busybox vi editor.
BusyBox was originally written to support the Debian Rescue/Install disks, but
it also makes an excellent environment for any small or embedded system.
Busybox in general will build on any architecture supported by gcc. It has
a few specialized features added for __sparc__ and __alpha__. insmod
- functionality is currently limited to x86, ARM, and SH3/4.
+ functionality is currently limited to x86, ARM, SH3/4, powerpc, and MIPS.
Supported libcs:
Subject: /bin/true doesn't work
Package: busybox
- Version: 0.48
+ Version: 0.51
When I invoke '/bin/true' it doesn't work. I expected it to return
a "0" but it returned a "1" instead. Here is the transcript:
Erik Andersen
<andersen@lineo.com>
<andersee@debian.org>
+ <andersee@codepoet.org>
<blatant plug>
Many thanks to go to Lineo for paying me to work on busybox.