BusyBox uses the name it was invoked under to determine which applet is
being invoked. (Try "mv busybox ls" and then "./ls -l".) Installing
busybox consists of creating symlinks (or hardlinks) to the busybox
- binary for each applet in busybox, and making sure these symlinks are in
- the shell's command $PATH. ("make install" creates these symlinks, and
- "make install-hardlinks" creates hardlinks instead.) The special applet
- name "busybox" (or with any optional suffix, such as "busybox-static")
- uses the first argument to determine which applet to run, as shown above.
+ binary for each applet in busybox, and making sure these links are in
+ the shell's command $PATH. The special applet name "busybox" (or with
+ any optional suffix, such as "busybox-static") uses the first argument
+ to determine which applet to run, as shown above.
</p>
<p>
BusyBox also has a feature called the "standalone shell", where the busybox
<ul>
+ <li><b>31 October 2005 -- 1.1.0-pre1</b>
+ <p>The development branch of busybox is stable enough for wider testing, so
+ you can now download (temporarly location:
+ <a href="http://www.landley.net/busybox/busybox-1.1.0-pre1.tar.bz2">tarball</a>
+ <a href="http://www.landley.net/busybox/BusyBox.html">docs</a>)
+ the first prerelease of 1.1.0. This prerelease includes a lot of new
+ functionality: new applets, new features, and extensive rewrites of
+ several existing applets. This prerelease should be noticeably more
+ <a href="http://www.opengroup.org/onlinepubs/009695399/">standards
+ compliant</a> than earlier versions of busybox, although we're
+ still working out the <a href="http://bugs.busybox.net">bugs</a>.</p>
+
<li><b>16 August 2005 -- 1.01 is out</b>
<p>A new stable release (<a href="http://www.busybox.net/downloads/busybox-1.01.tar.bz2">BusyBox