BusyBox is a software suite that provides several Unix utilities in a single executable file. It runs in a variety of POSIX environments such as Linux, Android,[7] and FreeBSD,[8] 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",[9] 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, version 2.[6]

Busybox DG834Gt.PNG
Original author(s)Bruce Perens
Developer(s)Erik Andersen,[1] Rob Landley,[2] Denys Vlasenko[3] and others
Initial releaseNovember 4, 1999; 20 years ago (1999-11-04)[4]
Stable release1.31.1 (October 25, 2019; 12 months ago (2019-10-25)) [±][5]
Repository Edit this at Wikidata
Written inC
Operating systemUnix-like
Size2.1 MB (compressed "tar.bz2")



Originally written by Bruce Perens in 1995 and declared complete for his intended usage in 1996,[10] BusyBox initially 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 until late 2006, then Denys Vlasenko took over as the current maintainer.

GPLv2/GPLv3 controversiesEdit

In September 2006, after heavy discussions and controversies between project maintainer Rob Landley and Bruce Perens,[11] the BusyBox[12][13] project decided against adopting the GNU Public License Version 3 (GPLv3); the BusyBox license was clarified as being GPL Version 2 (GPLv2) only.[14]

Since October 2006, Denys Vlasenko has taken over maintainership of BusyBox from Rob Landley, who has started Toybox, also as a result of the license controversies.[12][15]

GPL lawsuitsEdit

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

What was claimed to be the first US lawsuit over a GPL violation concerned use of BusyBox in an embedded device. The lawsuit,[16] case 07-CV-8205 was filed on September 20, 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.[17]

On November 21, 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).[18][19] The Xterasys case was settled on December 17 for release of source code used and an undisclosed payment,[20] and the High-Gain Antennas case on March 6, 2008 for active license compliance and an undisclosed payment.[21] On December 7, 2007, a case was brought against Verizon Communications over its distribution of firmware for Actiontec routers;[22][23] 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.[24] Further suits were brought on June 9, 2008 against Bell Microproducts (case 08-CV-5270) and SuperMicro (case 08-CV-5269),[25] the Super Micro case being settled on July 23, 2008.[26] BusyBox and Bell Microproducts also settled out of court on October 17.[27]

On December 14, 2009, a new lawsuit was filed naming fourteen defendants including Best Buy, JVC, Samsung and others.[28][29][30] In February 2010 Samsung released its LN52A650 TV firmware under GPLv2,[31] which was used later as a reference by the SamyGO community project.[32]

On about August 3, 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.[33]

No other developers, including original author Bruce Perens and maintainer Dave Cinege, were represented in these actions or party to the settlements. On December 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".[34]


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.[35] An alternative for customization is the smaller 'hush' shell. "Msh" and "lash" used to be available.[36]

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.[37]

Single binaryEdit

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)[38] 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[39] 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 use much less storage space than a system built with the corresponding full versions of the utilities replaced by BusyBox. Research[40] 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.


The official BusyBox documentation lists an overview of the available commands and their command-line options.

List of BusyBox commands[41]


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 argv[0] to find the name by which it is called, and runs the appropriate command, for example just


after /bin/ls is linked to /bin/busybox. This works because the first argument passed to a program is the name used for the program call, in this case the argument would be "/bin/ls". Busybox would see that its "name" is "ls" and act like the "ls" program.

Appliances and receptionEdit

BusyBox is used by several operating systems running on embedded systems and is an essential component of distributions such as OpenWrt, OpenEmbedded (including the Yocto Project) and Buildroot. The Sharp Zaurus utilizes BusyBox extensively for ordinary Unix-like tasks performed on the system's shell.[42]

BusyBox is also an essential component of VMware ESXi.

It is necessary for several root applications on Android and is also preinstalled with some "1 Tap Root" solutions such as Kingo Root.

Controversy over ToyboxEdit

Toybox was started early 2006 under the GNU General Public License by former Busybox maintainer Rob Landley as a result of the controversies around GPLv3/GPLv2 discussions. At the end of 2011[43] it was re-licensed under the BSD License after the project went dormant.[44] On January 11, 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.[45] 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.[46] 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".[47][48]

See alsoEdit


  1. ^ "Erik Andersen's Homepage".
  2. ^ Active Projects, Rob Landley's website
  3. ^ Denys Vlasenko, BusyBox maintainer
  4. ^ http://www.softwarefreedom.org/resources/2009/busybox-complaint-2009-12-14.pdf[permanent dead link]
  5. ^ "Announce 1.31.1". Retrieved 2019-12-19.
  6. ^ a b "BusyBox".
  7. ^ BitCubate X. "BusyBox Classic".
  8. ^ "FreeBSD port overview".
  9. ^ The slogan for 'The Swiss Army Knife of Embedded Linux' source
  10. ^ https://busybox.net/~landley/forensics.txt
  11. ^ Statement on Busybox Lawsuits on Bruce Perens' Weblog (2009-12-15, archived)
  12. ^ a b corbet (2006-10-01). "Busy busy busybox". lwn.net. Retrieved 2015-11-21. Since BusyBox can be found in so many embedded systems, it finds itself at the core of the GPLv3 anti-DRM debate. [...]The real outcomes, however, are this: BusyBox will be GPLv2 only starting with the next release. It is generally accepted that stripping out the "or any later version" is legally defensible, and that the merging of other GPLv2-only code will force that issue in any case
  13. ^ Landley, Rob (2006-09-09). "Re: Move GPLv2 vs v3 fun…". lwn.net. Retrieved 2015-11-21. Don't invent a straw man argument please. I consider licensing BusyBox under GPLv3 to be useless, unnecessary, overcomplicated, and confusing, and in addition to that it has actual downsides. 1) Useless: We're never dropping GPLv2.
  14. ^ GPL version 2 only for BusyBox 1.3.0. on lwn.net
  15. ^ Landley, Robert (2006-09-30). "I'm going out now. I may be some time". busybox (Mailing list).
  16. ^ a b On Behalf of BusyBox Developers Andersen and Landley, SFLC Files First Ever U.S. GPL Violation Lawsuit (Software Freedom Law Center September 20, 2007)
  17. ^ Settlement reached in Busybox-Monsoon GPL case Archived 2008-09-24 at the Wayback Machine (Bruce Byfield, Linux.com, October 30, 2007)
  18. ^ Linux legal team sues over GPL violations (Martin LaMonica, CNET News.com, November 21, 2007)
  19. ^ "Second Round of GPL Infringement Lawsuits Filed on Behalf of BusyBox Developers".
  20. ^ "BusyBox Developers and Xterasys Corporation Agree to Settle GPL Lawsuit".
  21. ^ BusyBox Developers and High-Gain Antennas Agree to Dismiss GPL Lawsuit (SFLC press release)
  22. ^ Open-source legal group strikes again on BusyBox, suing Verizon Archived 2007-12-10 at the Wayback Machine (Grant Gross, Computerworld, December 7, 2007)
  23. ^ "BusyBox Developers File GPL Infringement Lawsuit Against Verizon Communications".
  24. ^ Verizon Settles Open Source Software Lawsuit (Paul McDougell, InformationWeek, March 17, 2008)
  25. ^ SFLC Files Another Round of GPL Violation Lawsuits on Behalf of BusyBox Developers (SFLC press release)
  26. ^ BusyBox Developers and Supermicro Agree to End GPL Lawsuit: Good Faith Discussions Result in Dismissal of Copyright Infringement Case (SFLC press release)
  27. ^ 2008. Andersen v. Bell Microproducts, Inc., No. 08-cv-5270, Doc. No. 16 (S.D.N.Y. Oct. 17, 2008) (notice of voluntary dismissal)
  28. ^ Jason Perlow (December 16, 2009). "How to avoid modern day public GPL floggings". zdnet.com. Retrieved 2016-03-24. Public floggings and executions like the recent SFLC lawsuit could be avoided if actual standards and procedures for compliance with the GPL and other Free and Open Source licenses actually existed.
  29. ^ Best Buy, Samsung, Westinghouse, 11 more named in GPL lawsuit on cnet.com
  30. ^ The Software Freedom Conservancy, Inc. & Mr. Erik Andersen vs BestBuy, Samung, Westinghouse, JVC, Western Digital, Bosch, Phoebe Micro, Humax, ... (New York, 2009)
  31. ^ Visual Display - Open Source on samsung.com "Please download the links below We use GPLv2 and LGPLv2.1, not GPLv3 and LGPLv3. Model: LN40A650 / LN52A650 / LN52A750 [...] LN52A750.zip" (archived 2010)
  32. ^ Main_Page on samygo.tv
  33. ^ Jones, Pamela (2010-08-03). "BusyBox and the GPL Prevail Again - Updated 4Xs". Groklaw. Retrieved 2012-09-27.
  34. ^ Bruce Perens, "Statement on Busybox lawsuits", perens.com (December 15, 2009).
  35. ^ "ash variants". Archived from the original on 2010-03-10. Retrieved 2008-05-15.
  36. ^ "Use the new 'select' option to make the shell config". 2003-08-08. Retrieved 2019-04-02. The 'ash' shell adds about 60k in the default configuration and is the most complete and most pedantically correct shell included with busybox. This shell is actually a derivative of the Debian 'dash' shell (by Herbert Xu), which was created by porting the 'ash' shell (written by Kenneth Almquist) from NetBSD.
  37. ^ BusyBox - The Swiss Army Knife of Embedded Linux
  38. ^ "BusyBox simplifies embedded Linux systems: A small toolkit for small environments". IBM. Archived from the original on 2008-12-09.
  39. ^ crunchgen man page at freebsd.org Archived June 22, 2007, at the Wayback Machine
  40. ^ Doug Thayer, Keith Miller (April 16–17, 2004). "Four UNIX Programs in Four UNIX Collections: Seeking Consistency in an Open Source Icon" (PDF). Proceedings of Midwest Instruction and Computing Symposium. University of Minnesota, Morris.
  41. ^ "BusyBox Command Help". Retrieved 2013-02-24.
  42. ^ "Linux on the Road".
  43. ^ Landley, Rob. "License change commit". Toybox mercurial repository. Retrieved July 24, 2015.
  44. ^ http://landley.net/toybox/
  45. ^ "Busybox replacement project". 2012-01-11. Retrieved 2014-03-04.
  46. ^ "Garrett: The ongoing fight against GPL enforcement". LWN.net. 2012-01-31. Retrieved 2014-03-04. The real problem here is that the [Software Freedom Conservancy's] reliance on Busybox means that they're only able to target infringers who use that Busybox code. No significant kernel copyright holders have so far offered to allow the SFC to enforce their copyrights, with the result that enforcement action will grind to a halt as vendors move over to this Busybox replacement.
  47. ^ "Garrett: The ongoing fight against GPL enforcement". LWN.net. 2012-01-31. Retrieved 2014-03-04. >As the ex-maintainer of busybox who STARTED those lawsuits in the first place and now HUGELY REGRETS ever having done so, I think I'm entitled to stop the lawsuits in whatever way I see fit. They never resulted in a single line of code added to the busybox repository. They HAVE resulted in more than one company exiting Linux development entirely and switching to non-Linux operating systems for their embedded products, and they're a big part of the reason behind Android's "No GPL in userspace" policy.
  48. ^ Proffitt, Brian (2012-02-02). "GPL enforcement sparks community flames - Throwing the GPL baby out with the enforcement bath water?". ITworld. Retrieved 2015-03-04.

Further readingEdit

External linksEdit