docs/busybox.net/license.html - codeaurora/busybox - Gitiles

 <!--#include file="header.html" -->

 <p>
 <h3>BusyBox is licensed under the GNU General Public License</h3>

 <p>BusyBox is licensed under <a href="http://www.gnu.org/licenses/gpl.html#SEC1">the
 GNU General Public License</a> version 2, which is generally
 abbreviated as the GPL.  (This is the same license the Linux kernel is under,
 so you may be somewhat familiar with it by now.)</p>

 <p><a href="/products.html">Anyone thinking of shipping BusyBox as part of a
 product</a> should be familiar with the licensing terms under which they are
 allowed to use and distribute BusyBox.  Read the full test of the GPL (either
 through the above link, or in the file LICENSE in the busybox tarball), and
 also read the <a href="http://www.gnu.org/licenses/gpl-faq.html">Frequently
 Asked Questions about the GPL</a>.</p>

 <p>Basically, if you distribute GPL software the license requires that you also
 distribute the source code to that GPL-licensed software.  So if you distribute
 BusyBox without making the source code to the version you distribute available,
 you violate the license terms, and thus infringe on the copyrights of BusyBox.
 (This requirement applies whether or not you modified BusyBox; either way the
 license terms still apply to you.)  Read the license text for the details.</p>

 <p>BusyBox's copyrights are enforced by the <a
 href="http://www.softwarefreedom.org">Software Freedom Law Center</a>, which
 "accepts primary responsibility for enforcement of US copyrights on the
 software... and coordinates international copyright enforcement efforts for
 such works as necessary."  If you distribute BusyBox in a way that doesn't
 comply with the terms of the license BusyBox is distributed under, expect to
 hear from these guys.  Their entire reason for existing is to do pro-bono
 legal work for free/open source software projects.  (We used to list people who
 violate the BusyBox license in <a href="/shame.html">The Hall of Shame</a>,
 but these days we find it much more effective to hand them over to the
 lawyers.)</p>

 <p>Our enforcement efforts are aimed at bringing people into compliance with
 the BusyBox license.  Open source software is under a different license from
 proprietary software, but if you violate that license you're still a software
 pirate and the law gives the vendor (us) some big sticks to play with.  We
 don't want monetary awards, injunctions, or to generate bad PR for a company,
 unless that's the only way to get somebody that repeatedly ignores us to comply
 with the license on our code.</p>

 <h3>A Good Example</h3>

 <p>These days, <a href="http://www.linksys.com/">Linksys</a> is
 doing a good job at complying with the GPL, they get to be an
 example of how to do things right.  Please take a moment and
 check out what they do with
 <a href="http://www.linksys.com/servlet/Satellite?c=L_Content_C1&childpagename=US%2FLayout&cid=1115416836002&pagename=Linksys%2FCommon%2FVisitorWrapper">
 distributing the firmware for their WRT54G Router.</a>
 Following their example would be a fine way to ensure that you
 have also fulfilled your licensing obligations.</p>

 <!--#include file="footer.html" -->
	<!--#include file="header.html" -->

	<p>
	<h3>BusyBox is licensed under the GNU General Public License</h3>

	<p>BusyBox is licensed under <a href="http://www.gnu.org/licenses/gpl.html#SEC1">the
	GNU General Public License</a> version 2, which is generally
	abbreviated as the GPL. (This is the same license the Linux kernel is under,
	so you may be somewhat familiar with it by now.)</p>

	<p><a href="/products.html">Anyone thinking of shipping BusyBox as part of a
	product</a> should be familiar with the licensing terms under which they are
	allowed to use and distribute BusyBox. Read the full test of the GPL (either
	through the above link, or in the file LICENSE in the busybox tarball), and
	also read the <a href="http://www.gnu.org/licenses/gpl-faq.html">Frequently
	Asked Questions about the GPL</a>.</p>

	<p>Basically, if you distribute GPL software the license requires that you also
	distribute the source code to that GPL-licensed software. So if you distribute
	BusyBox without making the source code to the version you distribute available,
	you violate the license terms, and thus infringe on the copyrights of BusyBox.
	(This requirement applies whether or not you modified BusyBox; either way the
	license terms still apply to you.) Read the license text for the details.</p>

	<p>BusyBox's copyrights are enforced by the <a
	href="http://www.softwarefreedom.org">Software Freedom Law Center</a>, which
	"accepts primary responsibility for enforcement of US copyrights on the
	software... and coordinates international copyright enforcement efforts for
	such works as necessary." If you distribute BusyBox in a way that doesn't
	comply with the terms of the license BusyBox is distributed under, expect to
	hear from these guys. Their entire reason for existing is to do pro-bono
	legal work for free/open source software projects. (We used to list people who
	violate the BusyBox license in <a href="/shame.html">The Hall of Shame</a>,
	but these days we find it much more effective to hand them over to the
	lawyers.)</p>

	<p>Our enforcement efforts are aimed at bringing people into compliance with
	the BusyBox license. Open source software is under a different license from
	proprietary software, but if you violate that license you're still a software
	pirate and the law gives the vendor (us) some big sticks to play with. We
	don't want monetary awards, injunctions, or to generate bad PR for a company,
	unless that's the only way to get somebody that repeatedly ignores us to comply
	with the license on our code.</p>

	<h3>A Good Example</h3>

	<p>These days, <a href="http://www.linksys.com/">Linksys</a> is
	doing a good job at complying with the GPL, they get to be an
	example of how to do things right. Please take a moment and
	check out what they do with
	<a href="http://www.linksys.com/servlet/Satellite?c=L_Content_C1&childpagename=US%2FLayout&cid=1115416836002&pagename=Linksys%2FCommon%2FVisitorWrapper">
	distributing the firmware for their WRT54G Router.</a>
	Following their example would be a fine way to ensure that you
	have also fulfilled your licensing obligations.</p>

	<!--#include file="footer.html" -->