1 Please see the LICENSE file for copyright information.
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 has been written with size-optimization and limited resources in mind.
12 It is also extremely modular so you can easily include or exclude commands (or
13 features) at compile time. This makes it easy to customize your embedded
14 systems. To create a working system, just add a kernel and an editor (such as
15 e3 (http://www.sax.de/~adlibiti) or elvis-tiny).
17 BusyBox was originally written to support the Debian Rescue/Install disks, but
18 it also makes an excellent environment for any small or embedded system.
20 As of version 0.20 there is now a version number. : ) Also as of version 0.20,
21 BusyBox is now modularized to easily allow you to build only the components you
22 need, thereby reducing binary size. To turn off unwanted BusyBox components,
23 simply edit the file "Config.h" and comment out the components you do not need
24 using C++ style (//) comments.
26 After the build is complete, a busybox.links file is generated. This is
27 used by 'make install' to create symlinks to the busybox binary for all
28 compiled in functions. By default, 'make install' will place the symlink
29 forest into `pwd`/_install unless you have defined the PREFIX environment
30 variable (i.e., make PREFIX="/tmp/foo" install)
36 When you find you need help, you can check out the BusyBox mailing list
37 archives at http://opensource.lineo.com/lists/busybox/ or even join
38 the mailing list if you are interested.
44 If you find bugs, please submit a bug report. Full instructions on how to
45 report a bug are found at http://bugs.lineo.com/Reporting.html.
47 For the impatient: To submit a bug, simply send an email describing the problem
48 to submit@bugs.lineo.com. Bug reports should look something like this:
50 To: submit@bugs.lineo.com
51 From: diligent@testing.linux.org
52 Subject: /bin/true doesn't work
57 When I invoke '/bin/true' it doesn't work. I expected it to return
58 a "0" but it returned a "1" instead. Here is the transcript:
61 With GNU /bin/true, I get the following output:
64 I am using Debian 2.2r2, kernel version 2.2.18, and the latest
65 uClibc from CVS. Thanks for the wonderful program!
68 Note the careful description and use of examples showing not only what BusyBox
69 does, but also a counter example showing what an equivalent GNU app does. Bug
70 reports lacking such detail may take a _long_ time to be fixed... Thanks for
77 Source for the latest released version can always be downloaded from
78 ftp://ftp.lineo.com/pub/busybox.
84 BusyBox now has its own publicly browsable CVS tree at:
85 http://opensource.lineo.com/cgi-bin/cvsweb/busybox/
87 Anonymous CVS access is available. For instructions, check out:
88 http://opensource.lineo.com/cvs_anon.html
90 For those that are actively contributing there is even CVS write access:
91 http://opensource.lineo.com/cvs_write.html
95 Please feed suggestions, bug reports, insults, and bribes back to:
101 Many thanks to go to Lineo for paying me to work on busybox.