diff options
| author | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-11-29 22:12:19 +0000 |
|---|---|---|
| committer | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-11-29 22:12:19 +0000 |
| commit | e44be671ff4ea2d2dcb4e5a31feacb94d2684ed6 (patch) | |
| tree | bd2c5247894aaf7f59a01bf47ec9929407e3f8aa | |
| parent | 5f1dd9986842282987218d6fdfce6aa5303c51d6 (diff) | |
| download | busybox-w32-e44be671ff4ea2d2dcb4e5a31feacb94d2684ed6.tar.gz busybox-w32-e44be671ff4ea2d2dcb4e5a31feacb94d2684ed6.tar.bz2 busybox-w32-e44be671ff4ea2d2dcb4e5a31feacb94d2684ed6.zip | |
Moar Speling fickes frum Larry Doolittle
git-svn-id: svn://busybox.net/trunk/busybox@1348 69ca8d6d-28ef-0310-b511-8ec308f3f277
| -rw-r--r-- | README | 16 | ||||
| -rw-r--r-- | docs/style-guide.txt | 6 |
2 files changed, 11 insertions, 11 deletions
| @@ -4,7 +4,7 @@ BusyBox combines tiny versions of many common UNIX utilities into a single | |||
| 4 | small executable. It provides minimalist replacements for most of the utilities | 4 | small executable. It provides minimalist replacements for most of the utilities |
| 5 | you usually find in fileutils, shellutils, findutils, textutils, grep, gzip, | 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 | 6 | tar, etc. BusyBox provides a fairly complete POSIX environment for any small or |
| 7 | emdedded system. The utilities in BusyBox generally have fewer options then | 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 | 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. | 9 | the expected functionality and behave very much like their GNU counterparts. |
| 10 | 10 | ||
| @@ -14,20 +14,20 @@ features) at compile time. This makes it easy to customize your embedded | |||
| 14 | systems. To create a working system, just add a kernel, a shell (such as ash), | 14 | systems. To create a working system, just add a kernel, a shell (such as ash), |
| 15 | and an editor (such as elvis-tiny or ae). | 15 | and an editor (such as elvis-tiny or ae). |
| 16 | 16 | ||
| 17 | Busybox was originally written to support the Debian Rescue/Install disks, but | 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. | 18 | it also makes an excellent environment for any small or embedded system. |
| 19 | 19 | ||
| 20 | As of version 0.20 there is a version number. : ) Also as of version 0.20, | 20 | As of version 0.20 there is a version number. : ) Also as of version 0.20, |
| 21 | BusyBox is now modularized to easily allow you to build only the components you | 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, | 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 | 23 | simply edit the file "Config.h" and comment out the components you do not |
| 24 | need using C++ style (//) comments. | 24 | need using C++ style (//) comments. |
| 25 | 25 | ||
| 26 | After the build is complete a busybox.links file is generated which is then | 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 | 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 | 28 | compiled in functions. By default, 'make install' will place the symlink |
| 29 | forest into `pwd`/_install unless you have defined the PREFIX environment | 29 | forest into `pwd`/_install unless you have defined the PREFIX environment |
| 30 | variable (i.e. make PREFIX="/tmp/foo" install) | 30 | variable (i.e., make PREFIX="/tmp/foo" install) |
| 31 | 31 | ||
| 32 | ---------------- | 32 | ---------------- |
| 33 | Getting help: | 33 | Getting help: |
| @@ -48,7 +48,7 @@ Source for the latest released version can always be downloaded from | |||
| 48 | 48 | ||
| 49 | ---------------- | 49 | ---------------- |
| 50 | CVS: | 50 | CVS: |
| 51 | BusyBox now has its own publically browsable CVS tree at: | 51 | BusyBox now has its own publicly browsable CVS tree at: |
| 52 | http://opensource.lineo.com/cgi-bin/cvsweb/busybox/ | 52 | http://opensource.lineo.com/cgi-bin/cvsweb/busybox/ |
| 53 | 53 | ||
| 54 | Anonymous CVS access is available. For instructions, check out: | 54 | Anonymous CVS access is available. For instructions, check out: |
| @@ -65,7 +65,7 @@ Please feed suggestions, bug reports, insults, and bribes back to: | |||
| 65 | <andersen@lineo.com> | 65 | <andersen@lineo.com> |
| 66 | <andersee@debian.org> | 66 | <andersee@debian.org> |
| 67 | 67 | ||
| 68 | <blatent plug> | 68 | <blatant plug> |
| 69 | Many thanks to go to Lineo for paying me to work on busybox. | 69 | Many thanks to go to Lineo for paying me to work on busybox. |
| 70 | </blatent plug> | 70 | </blatant plug> |
| 71 | 71 | ||
diff --git a/docs/style-guide.txt b/docs/style-guide.txt index 9ea236024..4d0c7ca17 100644 --- a/docs/style-guide.txt +++ b/docs/style-guide.txt | |||
| @@ -354,7 +354,7 @@ The only time we deviate from emulating the GNU behavior is when: | |||
| 354 | switch) | 354 | switch) |
| 355 | - Emulating the GNU behavior is prohibitively expensive (lots more code | 355 | - Emulating the GNU behavior is prohibitively expensive (lots more code |
| 356 | would be required, lots more memory would be used, etc.) | 356 | would be required, lots more memory would be used, etc.) |
| 357 | - The differce is minor or cosmetic | 357 | - The difference is minor or cosmetic |
| 358 | 358 | ||
| 359 | A note on the 'cosmetic' case: Output differences might be considered | 359 | A note on the 'cosmetic' case: Output differences might be considered |
| 360 | cosmetic, but if the output is significant enough to break other scripts that | 360 | cosmetic, but if the output is significant enough to break other scripts that |
| @@ -367,7 +367,7 @@ Scope | |||
| 367 | If a const variable is used only in a single source file, put it in the source | 367 | If a const variable is used only in a single source file, put it in the source |
| 368 | file and not in a header file. Likewise, if a const variable is used in only | 368 | file and not in a header file. Likewise, if a const variable is used in only |
| 369 | one function, do not make it global to the file. Instead, declare it inside | 369 | one function, do not make it global to the file. Instead, declare it inside |
| 370 | the function body. Bottom line: Make a concious effort to limit declarations | 370 | the function body. Bottom line: Make a conscious effort to limit declarations |
| 371 | to the smallest scope possible. | 371 | to the smallest scope possible. |
| 372 | 372 | ||
| 373 | Inside applet files, all functions should be declared static so as to keep the | 373 | 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: | |||
| 434 | .... | 434 | .... |
| 435 | 435 | ||
| 436 | The only time you would ever need to use the old declaration syntax is to | 436 | The only time you would ever need to use the old declaration syntax is to |
| 437 | support ancient, antedeluvian compilers. To our good fortune, we have access | 437 | support ancient, antediluvian compilers. To our good fortune, we have access |
| 438 | to more modern compilers and the old declaration syntax is neither necessary | 438 | to more modern compilers and the old declaration syntax is neither necessary |
| 439 | nor desired. | 439 | nor desired. |
| 440 | 440 | ||
