emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Moar Speling fickes frum Larry Doolittle

Browse Source
This commit is contained in:
Eric Andersen 2000-11-29 22:12:19 +00:00
parent 20ea5c3352
commit 0730943b49
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README
View File

@ -4,7 +4,7 @@ BusyBox combines tiny versions of many common UNIX utilities into a single
small executable. It provides minimalist replacements for most of the utilities small executable. It provides minimalist replacements for most of the utilities
you usually find in fileutils, shellutils, findutils, textutils, grep, gzip, you usually find in fileutils, shellutils, findutils, textutils, grep, gzip,
tar, etc. BusyBox provides a fairly complete POSIX environment for any small or tar, etc. BusyBox provides a fairly complete POSIX environment for any small or
emdedded system. The utilities in BusyBox generally have fewer options then embedded system. The utilities in BusyBox generally have fewer options than
their full featured GNU cousins; however, the options that are included provide their full featured GNU cousins; however, the options that are included provide
the expected functionality and behave very much like their GNU counterparts. the expected functionality and behave very much like their GNU counterparts.
@ -14,20 +14,20 @@ features) at compile time. This makes it easy to customize your embedded
systems. To create a working system, just add a kernel, a shell (such as ash), systems. To create a working system, just add a kernel, a shell (such as ash),
and an editor (such as elvis-tiny or ae). and an editor (such as elvis-tiny or ae).
Busybox was originally written to support the Debian Rescue/Install disks, but BusyBox was originally written to support the Debian Rescue/Install disks, but
it also makes an excellent environment for any small or embedded system. it also makes an excellent environment for any small or embedded system.
As of version 0.20 there is a version number. : ) Also as of version 0.20, As of version 0.20 there is a version number. : ) Also as of version 0.20,
BusyBox is now modularized to easily allow you to build only the components you BusyBox is now modularized to easily allow you to build only the components you
need, thereby reducing binary size. To turn off unwanted Busybox components, need, thereby reducing binary size. To turn off unwanted BusyBox components,
simply edit the file "Config.h" and comment out the components you do not simply edit the file "Config.h" and comment out the components you do not
need using C++ style (//) comments. need using C++ style (//) comments.
After the build is complete a busybox.links file is generated which is then After the build is complete, a busybox.links file is generated. This is
used by 'make install' to create symlinks to the busybox binary for all used by 'make install' to create symlinks to the busybox binary for all
compiled in functions. By default, 'make install' will place the symlink compiled in functions. By default, 'make install' will place the symlink
forest into `pwd`/_install unless you have defined the PREFIX environment forest into `pwd`/_install unless you have defined the PREFIX environment
variable (i.e. make PREFIX="/tmp/foo" install) variable (i.e., make PREFIX="/tmp/foo" install)
---------------- ----------------
Getting help: Getting help:
@ -48,7 +48,7 @@ Source for the latest released version can always be downloaded from
---------------- ----------------
CVS: CVS:
BusyBox now has its own publically browsable CVS tree at: BusyBox now has its own publicly browsable CVS tree at:
http://opensource.lineo.com/cgi-bin/cvsweb/busybox/ http://opensource.lineo.com/cgi-bin/cvsweb/busybox/
Anonymous CVS access is available. For instructions, check out: Anonymous CVS access is available. For instructions, check out:
@ -65,7 +65,7 @@ Please feed suggestions, bug reports, insults, and bribes back to:
<andersen@lineo.com> <andersen@lineo.com>
<andersee@debian.org> <andersee@debian.org>
<blatent plug> <blatant plug>
Many thanks to go to Lineo for paying me to work on busybox. Many thanks to go to Lineo for paying me to work on busybox.
</blatent plug> </blatant plug>

6
docs/style-guide.txt
View File

@ -354,7 +354,7 @@ The only time we deviate from emulating the GNU behavior is when:
switch) switch)
- Emulating the GNU behavior is prohibitively expensive (lots more code - Emulating the GNU behavior is prohibitively expensive (lots more code
would be required, lots more memory would be used, etc.) would be required, lots more memory would be used, etc.)
- The differce is minor or cosmetic - The difference is minor or cosmetic
A note on the 'cosmetic' case: Output differences might be considered A note on the 'cosmetic' case: Output differences might be considered
cosmetic, but if the output is significant enough to break other scripts that cosmetic, but if the output is significant enough to break other scripts that
@ -367,7 +367,7 @@ Scope
If a const variable is used only in a single source file, put it in the source If a const variable is used only in a single source file, put it in the source
file and not in a header file. Likewise, if a const variable is used in only file and not in a header file. Likewise, if a const variable is used in only
one function, do not make it global to the file. Instead, declare it inside one function, do not make it global to the file. Instead, declare it inside
the function body. Bottom line: Make a concious effort to limit declarations the function body. Bottom line: Make a conscious effort to limit declarations
to the smallest scope possible. to the smallest scope possible.
Inside applet files, all functions should be declared static so as to keep the Inside applet files, all functions should be declared static so as to keep the
@ -434,7 +434,7 @@ the parameter list and opening bracket. Example:
.... ....
The only time you would ever need to use the old declaration syntax is to The only time you would ever need to use the old declaration syntax is to
support ancient, antedeluvian compilers. To our good fortune, we have access support ancient, antediluvian compilers. To our good fortune, we have access
to more modern compilers and the old declaration syntax is neither necessary to more modern compilers and the old declaration syntax is neither necessary
nor desired. nor desired.