BusyBox

From Infogalactic: the planetary knowledge core
(Redirected from Busybox)
Jump to: navigation, search
BusyBox
BusyBoxLogo.png
Busybox DG834Gt.PNG
Original author(s) Bruce Perens
Developer(s) Erik Andersen,[1] Rob Landley,[2] Denys Vlasenko[3] and others
Initial release November 4, 1999; 25 years ago (1999-11-04)[4]
Stable release 1.24.2 (March 24, 2016; 8 years ago (2016-03-24)) [±][5]
Development status Active
Written in C
Operating system Unix-like
Size 2.1 MB
Type
License GNU GPLv2 only (versions 1.2.3 or later[6])
Website www.busybox.net

BusyBox is software that provides several stripped-down Unix tools in a single executable file. It runs in a variety of POSIX environments such as Linux, Android,[7][8][9] and FreeBSD,[10] although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. The authors dubbed it "The Swiss Army knife of Embedded Linux",[11] as the single executable replaces basic functions of more than 300 common commands. It is released as free software under the terms of the GNU General Public License v2.[6]

History

Origins

Originally written by Bruce Perens in 1995 and declared complete for his intended usage in 1996,[12] BusyBox originally aimed to put a complete bootable system on a single floppy disk that would serve both as a rescue disk and as an installer for the Debian distribution. Since that time, it has been extended to become the de facto standard core user space toolset for embedded Linux devices and Linux distribution installers. Since each Linux executable requires several kilobytes of overhead, having the BusyBox program combine over two hundred programs together often saves substantial disk space and system memory.

BusyBox was maintained by Enrique Zanardi and focused on the needs of the Debian boot-floppies installer system until early 1998, when Dave Cinege took it over for the Linux Router Project (LRP). Cinege made several additions, created a modularized build environment, and shifted BusyBox's focus into general high-level embedded systems. As LRP development slowed down in 1999, Erik Andersen, then of Lineo, Inc., took over the project and became the official maintainer between December 1999 and March 2006. During this time the Linux embedded marketplace exploded in growth, and BusyBox matured greatly, expanding both its user base and functionality. Rob Landley became the maintainer in 2005 and continued for several years.

GPLv2/GPLv3 controversies

In September 2006, after heavy discussions and controversies between project maintainer Rob Landley and Bruce Perens, the BusyBox[13][14] project decided against adopting the newly created GPLv3; in contrast it clarified its license to GPLv2 only.[15]

As of October  2006 Denys Vlasenko took over maintainership of BusyBox from Rob Landley, who started Toybox, also as result of the license controversies.[13][16]

GPL lawsuits

In late 2007, BusyBox also came to prominence for actively prosecuting violations of the terms of its license (the GPL) in the U.S. District Court for the Southern District of New York.[17]

What was claimed to be the first US lawsuit over a GPL violation concerned use of BusyBox in an embedded device. The lawsuit,[17] case 07-CV-8205 in the United States District Court for the Southern District of New York was filed on 20 September 2007 by the Software Freedom Law Center (SFLC) on behalf of Andersen and Landley against Monsoon Multimedia Inc., after BusyBox code was discovered in a firmware upgrade and attempts to contact the company had apparently failed. The case was settled with release of the Monsoon version of the source and payment of an undisclosed amount of money to Andersen and Landley.[18]

On 21 November 2007, the SFLC brought two similar lawsuits on behalf of Andersen and Landley against two more companies, Xterasys (case 07-CV-10455) and High-Gain Antennas (case 07-CV-10456).[19][20] The Xterasys case was settled on December 17 for release of source code used and an undisclosed payment,[21] and the High-Gain Antennas case on March 6, 2008 for active license compliance and an undisclosed payment.[22] On 7 December 2007, a case was brought against Verizon Communications over its distribution of firmware for Actiontec routers;[23][24] this case was settled March 17, 2008 on condition of license compliance, appointment of an officer to oversee future compliance with free software licenses, and payment of an undisclosed sum.[25] Further suits were brought on June 9, 2008 against Bell Microproducts (case 08-CV-5270) and Super Micro Computer (case 08-CV-5269),[26] the Super Micro case being settled on 23 July 2008.[27] BusyBox and Bell Microproducts also settled out of court on 17 October.[28]

On December 14, 2009, a new lawsuit was filed naming fourteen defendants including Best Buy, JVC, Samsung and others.[29]

On about Aug 03, 2010, BusyBox won from Westinghouse a default judgement of triple damages of $90,000 and lawyers' costs and fees of $47,865, and possession of "presumably a lot of high-def TVs" as infringing equipment in the lawsuit Software Freedom Conservancy v. Best Buy, et al., the GPL infringement case noted in the paragraph above.[30]

No other developers, including original author Bruce Perens and long time maintainer Dave Cinege, were represented in these actions or party to the settlements. On Dec. 15, 2009, Perens released a statement expressing his unhappiness with some aspects of the legal situation, and in particular alleged that the current BusyBox developers "appear to have removed some of the copyright statements of other Busybox developers, and appear to have altered license statements".[31]

Features

BusyBox can be customized to provide a subset of over two hundred utilities. It can provide most of the utilities specified in the Single Unix Specification (SUS) plus many others that a user would expect to see on a Linux system. BusyBox uses the Almquist shell, also known as A Shell, ash and sh.[32][33]

As it is a complete bootstrap system, it will further replace the init daemon and udev (or the latter-day systemd) using itself to be called as init on startup and mdev at hotplug time.

The BusyBox Web site provides a full list of the utilities implemented.[34]

Single binary

Typical computer programs have a separate binary (executable) file for each application. BusyBox is a single binary, which is a conglomerate of many applications, each of which can be accessed by calling the single BusyBox binary with various names (supported by having a symbolic link or hard link for each different name)[35] in a specific manner with appropriate arguments.

BusyBox benefits from the single binary approach, as it reduces the overhead introduced by the executable file format (typically ELF), and it allows code to be shared between multiple applications without requiring a library. This technique is similar to what is provided by the crunchgen[36] command in FreeBSD, the difference being that BusyBox provides simplified versions of the utilities (for example, an ls command without file sorting ability), while a crunchgen generated sum of all the utilities would offer the fully functional versions.

Sharing of the common code, along with routines written with size-optimization in mind, can make a BusyBox system much smaller than a system built with the corresponding full versions of the utilities replaced by BusyBox. Research[37] that compared GNU, BusyBox, asmutils and Perl implementations of the standard Unix commands showed that in some situations BusyBox may perform faster than other implementations, but not always.

Commands

The official BusyBox documentation lists an overview of the available commands and their command-line options.[38] The available commands include (expand for view):

Examples

Programs included in BusyBox can be run simply by adding their name as an argument to the BusyBox executable:

/bin/busybox ls

More commonly, the desired command names are linked (using hard or symbolic links) to the BusyBox executable; BusyBox reads the zero element of argv to find the name by which it is called, and runs the appropriate command, for example just

/bin/ls

after /bin/ls is linked to /bin/busybox.

Busybox would see that its "name" is "ls" and act like the "ls" program.

Appliances and Reception

BusyBox is used by several operating systems running on embedded systems.

Controversy over Toybox

Toybox was started early 2006 under the GNU General Public License by former Busybox maintainer Rob Landley as result on the controversies around GPLv3/GPLv2 discussions. At the end of 2011[39] it was re-licensed under the BSD License after the project went dormant.[40] On 11 January 2012, Tim Bird, a Sony employee, suggested creating an alternative to BusyBox which would not be under the GNU General Public License. He suggested it be based on the dormant Toybox.[41] In January 2012 the proposal of creating a BSD licensed alternative to the GPL licensed BusyBox project drew harsh criticism from Matthew Garrett for taking away the only relevant tool for copyright enforcement of the Software Freedom Conservancy group.[42] The starter of BusyBox based lawsuits, Rob Landley, responded that this was intentional as he came to the conclusion that the lawsuits resulted not in the hoped for positive outcomes and he wanted to stop them "in whatever way I see fit".[43][44]

See also

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=BusyBox&oldid=1278974"