diff options
| -rw-r--r-- | README | 9 | ||||
| -rw-r--r-- | TODO | 17 | ||||
| -rw-r--r-- | docs/busybox.net/index.html | 35 | ||||
| -rw-r--r-- | libbb/README | 15 |
4 files changed, 61 insertions, 15 deletions
@@ -11,9 +11,9 @@ the expected functionality and behave very much like their GNU counterparts. 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. @@ -71,7 +71,7 @@ to submit@bugs.lineo.com. Bug reports should look something like this: 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: @@ -115,6 +115,7 @@ Please feed suggestions, bug reports, insults, and bribes back to: 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. @@ -11,13 +11,14 @@ around to it some time. If you have any good ideas, please let me know. to happen. False alarm. Sorry about the confusion. * The busybox shell, lash, is really too weak for serious use, although it is - possible to run simple systems with it. BusyBox 0.49 was supposed to have - a new shell, updated to understand full Bourne grammer. Well, that simply - didn't happen in time for the release. A rewrite is in progress that will - result in a new shell that understands the full Bourne grammar. This new - shell is being championed by Larry Doolittle <ldoolitt@recycle.lbl.gov>, and - could use your help. Please see the work in progress at - http://doolittle.faludi.com/~larry/parser.html + possible to run many simple systems with it. BusyBox 0.49 was supposed to + have a new shell, updated to understand full Bourne grammer. Well, that + simply didn't happen in time for the release. A rewrite is in progress + that will result in a new shell that understands the full Bourne grammar. + This new shell is being championed by Larry Doolittle + <ldoolitt@recycle.lbl.gov>, and could use your help. Please see the work + in progress at http://doolittle.faludi.com/~larry/parser.html and help + us out. -Erik @@ -31,7 +32,7 @@ Possible apps to include some time: ----------- Write a fixup_globals function to do just that right before calling -non-forking applets. Or, just always fork... +non-forking applets. Or, just always fork in the shell... ----------------------- diff --git a/docs/busybox.net/index.html b/docs/busybox.net/index.html index 883e17d..3ef2ab8 100644 --- a/docs/busybox.net/index.html +++ b/docs/busybox.net/index.html @@ -45,9 +45,8 @@ the expected functionality and behave very much like their GNU counterparts. 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 kernel, and a shell. +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. <p> BusyBox is now maintained by @@ -83,6 +82,36 @@ To subscribe, go and visit <a href="http://opensource.lineo.com/mailman/listinfo <ul> + <li> <b>10 April 2001 -- BusyBox 0.51 released</b> + <br> + + BusyBox 0.51 (the "rock-solid release") is now out there. This + release adds only 2 new applets: env and vi. The vi applet, + contributed by Sterling Huxley, is very functional, and is only + 22k. This release fixes 3 critical bugs in the 0.50 release. + There were 2 potential segfaults in lash (the busybox shell) in + the 0.50 release which are now fixed. Another critical bug in + 0.50 which is now fixed: syslogd from 0.50 could potentially + deadlock the init process and thereby break your entire system. + <p> + + There are a number of improvements in this release as well. For + one thing, the wget applet is greatly improved. Dmitry Zakharov + added FTP support, and Laurence Anderson make wget fully RFC + compliant for HTTP 1.1. The mechanism for including utility + functions in previous releases was clumsy and error prone. Now + all utility functions are part of a new libbb library, which makes + maintaining utility functions much simpler. And BusyBox now + compiles on itanium systems (thanks to the Debian itanium porters + for letting me use their system!). + <p> + You can read the + <a href="ftp://oss.lineo.com/busybox/Changelog">changelog</a> for + complete details. BusyBox 0.51 can be downloaded from + <a href="ftp://oss.lineo.com/busybox">ftp://oss.lineo.com/busybox</a>. + <p>Have Fun! + <p> + <li> <b>Busybox Boot-Floppy Image</b> <p>Because you asked for it, we have made available a <a href= diff --git a/libbb/README b/libbb/README new file mode 100644 index 0000000..0e36f84 --- /dev/null +++ b/libbb/README @@ -0,0 +1,15 @@ +Please see the LICENSE file for copyright information. + +libbb is BusyBox's utility library. This all used to be in a single file +(utility.c to be specific). When I split utility.c up to create libbb, I did +not carefully fix up the copyright and licensing information. I'll do that for +the next release. + +For now, justtrust me that a bunch of people have worked on this stuff, +and it is all GPL'ed. + + Erik Andersen + <andersen@lineo.com> + <andersee@debian.org> + <andersee@codepoet.org> + |