1 Please see the LICENSE file for details on copying and usage.
3 BusyBox combines tiny versions of many common UNIX utilities into a single
4 small executable. It provides minimalist replacements for most of the utilities
5 you usually find in fileutils, shellutils, findutils, textutils, grep, gzip,
6 tar, etc. BusyBox provides a fairly complete POSIX environment for any small or
7 embedded system. The utilities in BusyBox generally have fewer options than
8 their full featured GNU cousins; however, the options that are included provide
9 the expected functionality and behave very much like their GNU counterparts.
11 BusyBox was originally written to support the Debian Rescue/Install disks, but
12 it also makes an excellent environment for any small or embedded system.
14 BusyBox has been written with size-optimization and limited resources in mind.
15 It is also extremely modular so you can easily include or exclude commands (or
16 features) at compile time. This makes it easy to customize your embedded
17 systems. To create a working system, just add /dev, /etc, and a kernel.
19 As of version 0.20 there is now a version number. : ) Also as of version 0.20,
20 BusyBox is now modularized to easily allow you to build only the components you
21 need, thereby reducing binary size. Run 'make config' or 'make menuconfig'
22 for select the functionality that you wish to enable.
24 After the build is complete, a busybox.links file is generated. This is
25 used by 'make install' to create symlinks to the busybox binary for all
26 compiled in functions. By default, 'make install' will place the symlink
27 forest into `pwd`/_install unless you have defined the PREFIX environment
28 variable (i.e., 'make PREFIX=/tmp/foo install')
30 If you wish to install hardlinks, rather than symlinks, you can use
31 'make install-hardlinks' instead.
35 Supported architectures:
37 Busybox in general will build on any architecture supported by gcc. It has
38 a few specialized features added for __sparc__ and __alpha__. insmod
39 functionality is currently limited to x86, ARM, SH3/4, powerpc, m68k,
44 glibc-2.0.x, glibc-2.1.x, glibc-2.2.x, Linux-libc5, uClibc. People
45 are looking at newlib and diet-libc, but consider them unsupported,
50 Full functionality requires Linux 2.0.x or better. A large fraction of the
51 code should run on just about anything. While the current code is fairly
52 Linux specific, it should be fairly easy to port the majority of the code
53 to, say, FreeBSD or Solaris, or MacOsX, or even Windows (if you are into that
60 lash is the very smallest shell (adds just 10k) and it is quite usable as
61 a command prompt, but it is not suitable for any but the most trivial
62 scripting (such as an initrd that calls insmod a few times) since it does
63 not understand Bourne shell grammer. It does handle pipes, redirects, and
64 job control though. Adding in command editing makes it a very nice
65 lightweight command prompt.
67 hush is also quite small (just 18k) and it has very complete Bourne shell
68 grammer. It handles if/then/else/fi just fine, but doesn't handle loops
69 like for/do/done or case/esac and such. It also currently has a problem
70 with job control. Using hush is not yet recommended.
72 msh: The minix shell (adds just 30k) is quite complete and handles things
73 like for/do/done, case/esac and all the things you expect a Bourne shell to
74 do. It is not always pedantically correct about Bourne shell grammer (try
75 running the shell testscript "tests/sh.testcases" on it and compare vs bash)
76 but for most things it works quite well. It also uses only vfork, so it can
77 be used on uClinux systems. This was only recently added, so there is still
78 room to shrink it further...
80 ash: This adds about 60k in the default configuration and is the most
81 complete and most pedantically correct shell included with busybox. This
82 shell was also recently added, and several people (mainly Vladimir and Erik)
83 have been working on it. There are a number of configurable things at the
84 top of ash.c as well, so check those out if you want to tweak things.
90 When you find you need help, you can check out the BusyBox mailing list
91 archives at http://busybox.net/lists/busybox/ or even join
92 the mailing list if you are interested.
98 If you find bugs, please submit a detailed bug report to the busybox mailing
99 list at busybox@busybox.net. A well-written bug report should include a
100 transcript of a shell session that demonstrates the bad behavior and enables
101 anyone else to duplicate the bug on their own machine. The following is such
104 To: busybox@busybox.net
105 From: diligent@testing.linux.org
106 Subject: /bin/date doesn't work
111 When I execute Busybox 'date' it produces unexpected results.
112 With GNU date I get the following output:
115 Wed Mar 21 14:19:41 MST 2001
117 But when I use BusyBox date I get this instead:
122 I am using Debian unstable, kernel version 2.4.19-rmk1 on an Netwinder,
123 and the latest uClibc from CVS. Thanks for the wonderful program!
127 Note the careful description and use of examples showing not only what BusyBox
128 does, but also a counter example showing what an equivalent GNU app does. Bug
129 reports lacking such detail may never be fixed... Thanks for understanding.
135 Source for the latest released version, as well as daily snapshots, can always
137 http://busybox.net/downloads/
143 BusyBox now has its own publicly browsable CVS tree at:
144 http://busybox.net/cgi-bin/cvsweb/busybox/
146 Anonymous CVS access is available. For instructions, check out:
147 http://busybox.net/cvs_anon.html
149 For those that are actively contributing there is even CVS write access:
150 http://busybox.net/cvs_write.html
154 Please feed suggestions, bug reports, insults, and bribes back to:
156 <andersen@codepoet.org>
157 <andersen@codepoet.org>