-0.53
+0.60.0
+
+ Note:
+
+ For this release I have bumped the version number to 0.60.0. This
+ reflects the fact that this release is intended to form a new stable
+ BusyBox release series. If you need to rely on a stable version of
+ BusyBox, you should plan on using the stable 0.60.x series. If bugs
+ show up then I will release 0.60.1, then 0.60.2, etc... This is also
+ intended to deal with the fact that the BusyBox build system will be
+ getting a major overhaul for the next release and I don't want that to
+ break products that people are shipping. To avoid that, the new build
+ system will be released as part of a new BusyBox development series
+ that will have some not-yet-decided-on odd version number. Once things
+ stabablize and the new build system is working for everyone, then I
+ will release that as a new stable release series.
Critical Bugfixes:
* Matt Kraai
Other Changes:
* Erik Andersen
- -- various little things
-- fixed busybox.spec so it should now work on redhat systems
-- fixed dos2unix and unix2dos so they should work once again
-- Adjustments to make busybox more uClinux friendly. Busybox
should now work on uClinux systems without needing and source
code changes (applets that won't work on uClinux systems are
now automagicaly disabled).
+ -- various things (cleanups, libc compatibility work, etc, etc)
* Jim Gleason <jimg@lineo.com>
-- Fixed for sed, where it failed to preserve whether or not the
line was previously altered when running a subst command.
#
PROG := busybox
-VERSION := 0.53pre
+VERSION := 0.60.0
BUILDTIME := $(shell TZ=UTC date -u "+%Y.%m.%d-%H:%M%z")
export VERSION
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 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.
+systems. To create a working system, just add /dev, /etc, and a kernel.
BusyBox was originally written to support the Debian Rescue/Install disks, but
it also makes an excellent environment for any small or embedded system.
a command prompt, but it is not suitable for any but the most trivial
scripting (such as an initrd that calls insmod a few times) since it does
not understand Bourne shell grammer. It does handle pipes, redirects, and
-job control though. Adding in command editing makes it very nice
+job control though. Adding in command editing makes it a very nice
lightweight command prompt.
hush is also quite small (just 18k) and it has very complete Bourne shell
grammer. It handles if/then/else/fi just fine, but doesn't handle loops
like for/do/done or case/esac and such. It also currently has a problem
-with job control.
+with job control. Using hush is not yet recommended.
msh: The minix shell (adds just 30k) is quite complete and handles things
like for/do/done, case/esac and all the things you expect a Bourne shell to
complete and most pedantically correct shell included with busybox. This
shell was also recently added, and several people (mainly Vladimir and Erik)
have been working on it. There are a number of configurable things at the
-top of ash.c as well, so check those out if you want to tweak things. The
-Posix math support is currently disabled (that bit of code was horrible) but
-will be restored for the next BusyBox release.
+top of ash.c as well, so check those out if you want to tweak things.
----------------
%define name busybox
%define epoch 0
-%define version 0.53pre
+%define version 0.60.0
%define release %(date -I | sed -e 's/-/_/g')
%define serial 1
+busybox (1:0.60.0-1) unstable; urgency=low
+
+ * New version released. See changelog for details.
+
+ -- Erik Andersen <andersee@debian.org> Thu, 2 Aug 2001 12:12:37 -0600
+
busybox (1:0.52-1.1) unstable; urgency=high
* Non-maintainer upload
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. You can even use
-the busybox shell and the busybox vi editor.
+systems. To create a working system, just add /dev, /etc, and a kernel.
<p>
BusyBox is now maintained by
<ul>
+ <li> <b>2 August 2001 -- BusyBox 0.60.0 released</b>
+ <br>
+ I am very pleased to announce the immediate availability of
+ BusyBox 0.60.0. I have personally tested this release with libc5, glibc,
+ and <a href="http://cvs.uclinux.org/uClibc.html">uClibc</a> on
+ x86, ARM, and powerpc using linux 2.2 and 2.4, and I know a number
+ of people using it on everything from ia64 to m68k with great success.
+ Everything seems to be working very nicely now, so getting a nice
+ stable bug-free(tm) release out seems to be in order. This releases fixes
+ a memory leak in syslogd, a number of bugs in the ash and msh shells, and
+ cleans up a number of things.
+
+ <p>
+
+ Those wanting an easy way to test the 0.60.0 release with uClibc can
+ use <a href="http://user-mode-linux.sourceforge.net/">User-Mode Linux</a>
+ to give it a try by downloading and compiling
+ <a href="ftp://oss.lineo.com/buildroot.tar.gz">buildroot.tar.gz</a>.
+ You don't have to be root or reboot your machine to run test this way.
+ Preconfigured User-Mode Linux kernel source is also on oss.lineo.com.
+ <p>
+ Another cool thing is the nifty <a href="ftp://oss.lineo.com/busybox/tutorial/index.html">
+ BusyBox Tutorial</a> contributed by K Computing. This requires
+ a ShockWave plugin (or standalone viewer), so you may want to grab the
+ the GPLed shockwave viewer from <a href="http://www.swift-tools.com/Flash/flash-0.4.10.tgz">here</a>
+ to view the tutorial.
+ <p>
+
+ Finally, In case you didn't notice anything odd about the
+ version number of this release, let me point out that this release
+ is <em>not</em> 0.53, because I bumped the version number up a
+ bit. This reflects the fact that this release is intended to form
+ a new stable BusyBox release series. If you need to rely on a
+ stable version of BusyBox, you should plan on using the stable
+ 0.60.x series. If bugs show up then I will release 0.60.1, then
+ 0.60.2, etc... This is also intended to deal with the fact that
+ the BusyBox build system will be getting a major overhaul for the
+ next release and I don't want that to break products that people
+ are shipping. To avoid that, the new build system will be
+ released as part of a new BusyBox development series that will
+ have some not-yet-decided-on odd version number. Once things
+ stabablize and the new build system is working for everyone, then
+ I will release that as a new stable release series.
+
+ <p>
+ The
+ <a href="ftp://oss.lineo.com/busybox/Changelog">changelog</a> has all
+ the details. As usual BusyBox 0.60.0 can be downloaded from
+ <a href="ftp://oss.lineo.com/busybox">ftp://oss.lineo.com/busybox</a>.
+ <p>Have Fun!
+ <p>
+
+
<li> <b>7 July 2001 -- BusyBox 0.52 released</b>
<br>
%define name busybox
%define epoch 0
-%define version 0.53pre
+%define version 0.60.0
%define release %(date -I | sed -e 's/-/_/g')
%define serial 1
projects / platform / upstream / busybox.git / commitdiff