prepare for release
This commit is contained in:
Eric Andersen
parent
9789bf1019
commit
9395ca4f68
@ -18,6 +18,7 @@ have additions to this FAQ document, we would love to add them,
|
||||
<li><a href="#demanding">I demand that you to add <favorite feature> right now! How come
|
||||
you don't answer all my questions on the mailing list instantly? I demand
|
||||
that you help me with all of my problems <em>Right Now</em>!</a>
|
||||
<li><a href="#getting_started">How can I get started using BusyBox?</a>
|
||||
<li><a href="#helpme">I need help with BusyBox! What should I do?</a>
|
||||
<li><a href="#contracts">I need you to add <favorite feature>! Are the BusyBox developers willing to
|
||||
be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide
|
||||
@ -144,6 +145,27 @@ have additions to this FAQ document, we would love to add them,
|
||||
run your shell on a real console...
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<h2><a name="getting_started">How can I get started using BusyBox?</a></h2>
|
||||
<p>
|
||||
|
||||
An easy method to build your own basic BusyBox based system, is to
|
||||
follow these simple steps:
|
||||
<ul>
|
||||
<li> Point your web browser <a href="/cgi-bin/cvsweb/buildroot/">here</a>
|
||||
<li> Click on "Download tarball"
|
||||
<li> Unpack the tarball on your Linux system somewhere
|
||||
<li> run 'make' and configure things to taste.
|
||||
<li> run 'unset CC'. Some Linux systems (i.e. Gentoo) set 'CC'
|
||||
in the system environment which messes up cross compiles.
|
||||
<li> run 'make'
|
||||
<li> go have lunch, drink a pop, call a friend, play a video game, etc
|
||||
till it finishes downloading software and compiling things.
|
||||
<li> You should now have a shiny new BusyBox based system.
|
||||
</ul>
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<h2><a name="demanding">I demand that you to add <favorite feature> right now! How come
|
||||
@ -198,8 +220,8 @@ have additions to this FAQ document, we would love to add them,
|
||||
href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid
|
||||
on your project. If Erik is too busy to personally add your feature, there
|
||||
are many other active BusyBox contributors who will almost certainly be able
|
||||
to help you out. Erik can contact them and ask them about their availability,
|
||||
and may even ask you to post your request for services on the mailing list.
|
||||
to help you out. Erik can contact them privatly, and may even let you to
|
||||
post your request for services on the mailing list.
|
||||
|
||||
|
||||
<hr />
|
||||
@ -218,7 +240,7 @@ have additions to this FAQ document, we would love to add them,
|
||||
<input type="hidden" name="cmd" value="_xclick">
|
||||
<input type="hidden" name="business" value="andersen@codepoet.org">
|
||||
<input type="hidden" name="item_name" value="Support BusyBox">
|
||||
<input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png">
|
||||
<input type="hidden" name="image_url" value="http://codepoet-consulting.com/images/codepoet.png">
|
||||
<input type="hidden" name="no_shipping" value="1">
|
||||
<input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal">
|
||||
</form>
|
||||
|
||||
@ -10,12 +10,32 @@ whatsoever, this page attempts to summarize what you should do to
|
||||
ensure you do not accidentally violate the law.
|
||||
|
||||
<p>
|
||||
<h3>Complying with the BusyBox license is easy and completely free.</h3>
|
||||
|
||||
U.S. and International Law protects copyright owners from the unauthorized
|
||||
reproduction, adaptation, display, distribution, etc of copyright protected
|
||||
works. Copyright violations (such as shipping BusyBox in a manner contrary to
|
||||
its license) are subject to severe penalties. The courts can award up to
|
||||
$150,000 per product shipped without even showing any actual loss by the
|
||||
copyright holder. Criminal penalties are available for intentional acts
|
||||
undertaken for purposes of "commercial advantage" or "private financial gain."
|
||||
In addition, if it comes to my attention that you are violating the BusyBox
|
||||
license, I will list you on the <a href="/shame.html">BusyBox Hall of Shame</a>
|
||||
webpage.
|
||||
|
||||
<p>
|
||||
|
||||
Nobody wants that to happen. Do everyone a favor and don't break the law -- if
|
||||
you use BusyBox, you <b>must comply with the BusyBox license</b>.
|
||||
|
||||
<p>
|
||||
<h3>BusyBox is licensed under the GNU General Public License</h3>
|
||||
|
||||
BusyBox is licensed under the GNU General Public License , which
|
||||
is generally just abbreviated simply as the GPL license, or
|
||||
just the GPL. <a href="/products.html">Anyone thinking of shipping
|
||||
is generally just abbreviated as the GPL license, or
|
||||
just the GPL.
|
||||
<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. You are advised to take a look over the
|
||||
@ -53,37 +73,39 @@ applications such as BusyBox is mandatory.
|
||||
|
||||
<p>
|
||||
|
||||
<b>Accompanied by source</b> generally means you place the full
|
||||
source code for all GPL'd products such as BusyBox on a driver CD
|
||||
somewhere. Full source code includes the BusyBox ".config" file
|
||||
used when your shipping BusyBox binary was compiled.
|
||||
<b>Accompanied by source</b> generally means you distribute the full
|
||||
source code for all GPL'd products including BusyBox along with your
|
||||
product, such as by placing it somewhere on a driver CD. Full source
|
||||
code includes the BusyBox ".config" file used when your shipping BusyBox
|
||||
binary was compiled, and any and all modifications you made to the
|
||||
BusyBox source code.
|
||||
|
||||
<p>
|
||||
|
||||
<b>A written offer</b> generally means that somewhere in the
|
||||
docs for your product, you write something like
|
||||
documentation for your product, you write something like
|
||||
|
||||
<blockquote>
|
||||
The GPL source code contained in this product is available as a
|
||||
free download from http://blah.blah.blah/
|
||||
</blockquote>
|
||||
Or you can offer source by writing
|
||||
somewhere in the docs for your product something like
|
||||
Alternatively, you can offer the source code by writing
|
||||
somewhere in the documentation for your product something like
|
||||
<blockquote>
|
||||
If you would like a copy of the GPL source code in this product
|
||||
on a CD, please send $9.99 to <address> for the costs of
|
||||
preparing and mailing a CD to you.
|
||||
If you would like a copy of the GPL source code contained in this
|
||||
product shipped to you on CD, please send $9.99 to <address>
|
||||
which covers the cost of preparing and mailing a CD to you.
|
||||
</blockquote>
|
||||
<p>
|
||||
|
||||
Keep in mind though that if you distribute GPL'd binaries online
|
||||
(as is often done when supplying firmware updates), it is highly
|
||||
recommended that you make the corresponding source available online
|
||||
at the same place. Regardless, you <b>must</b> either make source
|
||||
available online (i.e. <b>accompanied by source</b>) and/or inform
|
||||
those downloading firmware updates of their right to obtain source
|
||||
(i.e. <b>a written offer</b>). Failure to do so is a violation of
|
||||
your licensing obligations.
|
||||
Keep in mind though that if you distribute GPL'd binaries online (as is often
|
||||
done when supplying firmware updates), it is <b>highly</b> recommended that you
|
||||
make the corresponding source available online at the same place. Regardless,
|
||||
if you distribute a binary copy of BusyBox online (such as part of a firmware
|
||||
update) you <b>must</b> either make source available online (i.e.
|
||||
<b>accompanied by source</b>) and/or inform those downloading firmware updates
|
||||
of their right to obtain source (i.e. <b>a written offer</b>). Failure to do
|
||||
so is a violation of your licensing obligations.
|
||||
|
||||
|
||||
<p>
|
||||
@ -97,6 +119,7 @@ If you distribute any GPL'd binaries, you must also make source available
|
||||
as discussed on this webpage.
|
||||
|
||||
<p>
|
||||
<h3>A Good Example</h3>
|
||||
|
||||
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
|
||||
@ -104,8 +127,8 @@ example of how to do things right. Please take a moment and
|
||||
check out what they do with
|
||||
<a href="http://www.linksys.com/download/firmware.asp?fwid=178">
|
||||
distributing the firmware for their WRT54G Router.</a>
|
||||
Following their example would be a fine way to ensure you have
|
||||
fulfilled your licensing obligations.
|
||||
Following their example would be a fine way to ensure that you
|
||||
have also fulfilled your licensing obligations.
|
||||
|
||||
|
||||
<!--#include file="footer.html" -->
|
||||
|
||||
@ -3,142 +3,44 @@
|
||||
|
||||
<ul>
|
||||
|
||||
<li><b>16 August 2004 -- BusyBox 1.0.0-rc3 released</b><p>
|
||||
<li><b>13 October 2004 -- BusyBox 1.00 released</b><p>
|
||||
|
||||
When you take a careful look at nearly every embedded Linux device or
|
||||
software distribution shipping today, you will find a copy of BusyBox.
|
||||
With countless routers, set top boxes, wireless access points, PDAs, and
|
||||
who knows what else, the future for Linux and BusyBox on embedded devices
|
||||
is looking very bright.
|
||||
|
||||
Here goes release candidate 3...
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
It is therefore with great satisfaction that I declare each and every
|
||||
device already shipping with BusyBox is now officially out of date.
|
||||
The highly anticipated release of BusyBox 1.00 has arrived!
|
||||
|
||||
<p>
|
||||
|
||||
Over three years in development, BusyBox 1.00 represents a tremendous
|
||||
improvement over the old 0.60.x stable series. Now featuring a Linux
|
||||
KernelConf based configuration system (as used by the Linux kernel),
|
||||
Linux 2.6 kernel support, many many new applets, and the development
|
||||
work and testing of thousands of people from around the world.
|
||||
|
||||
<p>
|
||||
|
||||
If you are already using BusyBox, you are strongly encouraged to upgrade to
|
||||
BusyBox 1.00. If you are considering developing an embedded Linux device
|
||||
or software distribution, you may wish to investigate if using BusyBox is
|
||||
right for your application. If you need help getting started using
|
||||
BusyBox, if you wish to donate to help cover expenses, or if you find a bug
|
||||
and need help reporting it, you are invited to visit the <a
|
||||
href="FAQ.html">BusyBox FAQ</a>.
|
||||
|
||||
<p>
|
||||
|
||||
As usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
<li><b>26 July 2004 -- BusyBox 1.0.0-rc2 released</b><p>
|
||||
|
||||
Here goes release candidate 2...
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
<li><b>20 July 2004 -- BusyBox 1.0.0-rc1 released</b><p>
|
||||
|
||||
Here goes release candidate 1... This fixes all (most?) of the problems
|
||||
that have turned up since -pre10. In particular, loading and unloading of
|
||||
kernel modules with 2.6.x kernels should be working much better.
|
||||
<p>
|
||||
|
||||
I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no real
|
||||
reason why the 1.0.0 release shouldn't happen with things pretty much as
|
||||
is. BusyBox is in good shape at the moment, and it works nicely for
|
||||
everything that I'm doing with it. And from the reports I've been getting,
|
||||
it works nicely for what most everyone else is doing with it as well.
|
||||
There will eventually be a 1.0.1 anyway, so we might as well get on with
|
||||
it. No, BusyBox is not perfect. No piece of software ever is. And while
|
||||
there is still plenty that can be done to improve things, most of that work
|
||||
is waiting till we can get a solid 1.0.0 release out the door....
|
||||
<p>
|
||||
|
||||
Please do not bother to send in patches adding cool new features at this
|
||||
time. Only bug-fix patches will be accepted. If you have submitted a
|
||||
bug-fixing patch to the busybox mailing list and no one has emailed you
|
||||
explaining why your patch was rejected, it is safe to say that your patch
|
||||
has been lost or forgotten. That happens sometimes. Please re-submit your
|
||||
bug-fixing patch to the BusyBox mailing list, and be sure to put "[PATCH]"
|
||||
at the beginning of the email subject line!
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
On a less happy note, My 92 year old grandmother (my dad's mom) passed away
|
||||
yesterday (June 19th). The funeral will be Thursday in a little town about
|
||||
2 hours south of my home. I've checked and there is absolutely no way I
|
||||
could be back in time for the funeral if I attend <a
|
||||
href="http://www.linuxsymposium.org/2004/">OLS</a> and give my presentation
|
||||
as scheduled.
|
||||
<p>
|
||||
As such, it is with great reluctance and sadness that I have come
|
||||
to the conclusion I will have to make my appologies and skip OLS
|
||||
this year.
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>13 April 2004 -- BusyBox 1.0.0-pre10 released</b><p>
|
||||
|
||||
Ok, I lied. It turns out that -pre9 will not be the final BusyBox
|
||||
pre-release. With any luck however -pre10 will be, since I <b>really</b>
|
||||
want to get BusyBox 1.0.0 released very soon. As usual, please do not
|
||||
bother to send in patches adding cool new features at this time. Only
|
||||
bug-fix patches will be accepted. It would also be <b>very</b> helpful if
|
||||
people could continue to review the BusyBox documentation and submit
|
||||
improvements.
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>6 April 2004 -- BusyBox 1.0.0-pre9 released</b><p>
|
||||
|
||||
Here goes the final BusyBox pre-release... This is your last chance for
|
||||
bug fixes. With luck this will be released as BusyBox 1.0.0 later this
|
||||
week. Please do not bother to send in patches adding cool new features at
|
||||
this time. Only bug-fix patches will be accepted. It would also be
|
||||
<b>very</b> helpful if people could help review the BusyBox documentation
|
||||
and submit improvements. I've spent a lot of time updating the
|
||||
documentation to make it better match reality, but I could really use some
|
||||
assistance in checking that the features supported by the various applets
|
||||
match the features listed in the documentation.
|
||||
|
||||
<p>
|
||||
I had hoped to get this released a month ago, but
|
||||
<a href="http://codepoet.org/gallery/baby_peter/img_1796">
|
||||
another release on 1 March 2004</a> has kept me busy...
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>23 February 2004 -- BusyBox 1.0.0-pre8 released</b><p>
|
||||
|
||||
Here goes yet another BusyBox pre-release... Please do not bother to send
|
||||
in patches supplying new features at this time. Only bug-fix patches will
|
||||
be accepted. If you have a cool new feature you would like to see
|
||||
supported, or if you have an amazing new applet you would like to submit,
|
||||
please wait and submit such things later. We really want to get a release
|
||||
out we can all be proud of. We are still aiming to finish off the -pre
|
||||
series in February and move on to the final 1.0.0 release... So if you
|
||||
spot any bugs, now would be an excellent time to send in a fix to the
|
||||
busybox mailing list. It would also be <b>very</b> helpful if people could
|
||||
help review the BusyBox documentation and submit improvements. It would be
|
||||
especially helpful if people could check that the features supported by the
|
||||
various applets match the features listed in the documentation.
|
||||
|
||||
<p>
|
||||
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>Old News</b><p>
|
||||
<a href="/oldnews.html">Click here to read older news</a>
|
||||
|
||||
@ -3,6 +3,142 @@
|
||||
|
||||
<ul>
|
||||
|
||||
<li><b>16 August 2004 -- BusyBox 1.0.0-rc3 released</b><p>
|
||||
|
||||
Here goes release candidate 3...
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
<li><b>26 July 2004 -- BusyBox 1.0.0-rc2 released</b><p>
|
||||
|
||||
Here goes release candidate 2...
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
<li><b>20 July 2004 -- BusyBox 1.0.0-rc1 released</b><p>
|
||||
|
||||
Here goes release candidate 1... This fixes all (most?) of the problems
|
||||
that have turned up since -pre10. In particular, loading and unloading of
|
||||
kernel modules with 2.6.x kernels should be working much better.
|
||||
<p>
|
||||
|
||||
I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no real
|
||||
reason why the 1.0.0 release shouldn't happen with things pretty much as
|
||||
is. BusyBox is in good shape at the moment, and it works nicely for
|
||||
everything that I'm doing with it. And from the reports I've been getting,
|
||||
it works nicely for what most everyone else is doing with it as well.
|
||||
There will eventually be a 1.0.1 anyway, so we might as well get on with
|
||||
it. No, BusyBox is not perfect. No piece of software ever is. And while
|
||||
there is still plenty that can be done to improve things, most of that work
|
||||
is waiting till we can get a solid 1.0.0 release out the door....
|
||||
<p>
|
||||
|
||||
Please do not bother to send in patches adding cool new features at this
|
||||
time. Only bug-fix patches will be accepted. If you have submitted a
|
||||
bug-fixing patch to the busybox mailing list and no one has emailed you
|
||||
explaining why your patch was rejected, it is safe to say that your patch
|
||||
has been lost or forgotten. That happens sometimes. Please re-submit your
|
||||
bug-fixing patch to the BusyBox mailing list, and be sure to put "[PATCH]"
|
||||
at the beginning of the email subject line!
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
|
||||
<p>
|
||||
On a less happy note, My 92 year old grandmother (my dad's mom) passed away
|
||||
yesterday (June 19th). The funeral will be Thursday in a little town about
|
||||
2 hours south of my home. I've checked and there is absolutely no way I
|
||||
could be back in time for the funeral if I attend <a
|
||||
href="http://www.linuxsymposium.org/2004/">OLS</a> and give my presentation
|
||||
as scheduled.
|
||||
<p>
|
||||
As such, it is with great reluctance and sadness that I have come
|
||||
to the conclusion I will have to make my appologies and skip OLS
|
||||
this year.
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>13 April 2004 -- BusyBox 1.0.0-pre10 released</b><p>
|
||||
|
||||
Ok, I lied. It turns out that -pre9 will not be the final BusyBox
|
||||
pre-release. With any luck however -pre10 will be, since I <b>really</b>
|
||||
want to get BusyBox 1.0.0 released very soon. As usual, please do not
|
||||
bother to send in patches adding cool new features at this time. Only
|
||||
bug-fix patches will be accepted. It would also be <b>very</b> helpful if
|
||||
people could continue to review the BusyBox documentation and submit
|
||||
improvements.
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>6 April 2004 -- BusyBox 1.0.0-pre9 released</b><p>
|
||||
|
||||
Here goes the final BusyBox pre-release... This is your last chance for
|
||||
bug fixes. With luck this will be released as BusyBox 1.0.0 later this
|
||||
week. Please do not bother to send in patches adding cool new features at
|
||||
this time. Only bug-fix patches will be accepted. It would also be
|
||||
<b>very</b> helpful if people could help review the BusyBox documentation
|
||||
and submit improvements. I've spent a lot of time updating the
|
||||
documentation to make it better match reality, but I could really use some
|
||||
assistance in checking that the features supported by the various applets
|
||||
match the features listed in the documentation.
|
||||
|
||||
<p>
|
||||
I had hoped to get this released a month ago, but
|
||||
<a href="http://codepoet.org/gallery/baby_peter/img_1796">
|
||||
another release on 1 March 2004</a> has kept me busy...
|
||||
|
||||
<p>
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<p>
|
||||
<li><b>23 February 2004 -- BusyBox 1.0.0-pre8 released</b><p>
|
||||
|
||||
Here goes yet another BusyBox pre-release... Please do not bother to send
|
||||
in patches supplying new features at this time. Only bug-fix patches will
|
||||
be accepted. If you have a cool new feature you would like to see
|
||||
supported, or if you have an amazing new applet you would like to submit,
|
||||
please wait and submit such things later. We really want to get a release
|
||||
out we can all be proud of. We are still aiming to finish off the -pre
|
||||
series in February and move on to the final 1.0.0 release... So if you
|
||||
spot any bugs, now would be an excellent time to send in a fix to the
|
||||
busybox mailing list. It would also be <b>very</b> helpful if people could
|
||||
help review the BusyBox documentation and submit improvements. It would be
|
||||
especially helpful if people could check that the features supported by the
|
||||
various applets match the features listed in the documentation.
|
||||
|
||||
<p>
|
||||
|
||||
The <a href="downloads/Changelog">changelog</a> has all the details.
|
||||
And as usual you can <a href="downloads">download busybox here</a>.
|
||||
|
||||
<p>Have Fun!
|
||||
<p>
|
||||
|
||||
|
||||
<li><b>4 February 2004 -- BusyBox 1.0.0-pre7 released</b><p>
|
||||
|
||||
There was a bug in -pre6 that broke argument parsing for a
|
||||
|
||||
@ -71,17 +71,13 @@ nanoEngine</a>
|
||||
</li><li><a href="http://www.ltsp.org/">Linux Terminal
|
||||
Server Project</a>
|
||||
|
||||
</li><li><a href=
|
||||
"http://www.devil-linux.org/">Devil-Linux</a>
|
||||
</li><li><a href="http://www.devil-linux.org/">Devil-Linux</a>
|
||||
|
||||
</li><li><a href=
|
||||
"http://dutnux.sourceforge.net/">DutNux</a>
|
||||
</li><li><a href="http://dutnux.sourceforge.net/">DutNux</a>
|
||||
|
||||
</li><li><a href=
|
||||
"http://www.microwerks.net/~hugo/mindi/">Mindi</a>
|
||||
</li><li><a href="http://www.microwerks.net/~hugo/mindi/">Mindi</a>
|
||||
|
||||
</li><li><a href=
|
||||
"http://www.tzi.de/~pharao90/ttylinux">ttylinux</a>
|
||||
</li><li><a href="http://www.minimalinux.org/ttylinux/">ttylinux</a>
|
||||
|
||||
</li><li><a href="http://www.coyotelinux.com/">Coyote Linux</a>
|
||||
|
||||
@ -93,6 +89,7 @@ Image</a>
|
||||
</li><li><a href="http://tinfoilhat.cultists.net/">Tinfoil
|
||||
Hat Linux</a>
|
||||
|
||||
</li><li><a href="http://sourceforge.net/projects/gp32linux/">gp32linux</a>
|
||||
</li><li><a href="http://familiar.handhelds.org/">Familiar Linux</a><br>A linux distribution for handheld computers
|
||||
</li><li><a href="http://rescuecd.sourceforge.net/">Timo's Rescue CD Set</a>
|
||||
</li><li><a href="http://sf.net/projects/netstation/">Netstation</a>
|
||||
@ -149,6 +146,17 @@ Hat Linux</a>
|
||||
</li><li><a href="http://www.actiontec.com/products/broadband/54mbps_wireless_gateway_1p/index.html">
|
||||
ActionTec GT701-WG Wireless Gateway/DSL Modem</a>
|
||||
with source <a href="http://128.121.226.214/gtproducts/index.html">here</a>
|
||||
</li><li><a href="http://smartlinux.sourceforge.net/">S.M.A.R.T. Linux</a>
|
||||
</li><li><a href="http://www.dlink.com/">DLink - Model GSL-G604T, DSL-300T, and possibly other models</a>
|
||||
with source <a href="ftp://ftp.dlink.co.uk/dsl_routers_modems/">here,</a>
|
||||
with source <a href="ftp://ftp.dlink.de/dsl-products/">and here,</a>
|
||||
and quite possibly other places as well. You may need to dig down a bit
|
||||
to find the source, but it does seem to be there.
|
||||
</li><li><a href="http://www.siemens-mobile.de/cds/frontdoor/0,2241,de_de_0_42931_rArNrNrNrN,00.html">Siemens SE515 DSL router</a>
|
||||
with source <a href="http://now-portal.c-lab.de/projects/gigaset/">here, I think...</a>
|
||||
with some details <a href="http://heinz.hippenstiel.org/familie/hp/hobby/gigaset_se515dsl.html">here.</a>
|
||||
</li><li><a href="http://frwt.stim.ru/">Free Remote Windows Terminal</a>
|
||||
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -13,7 +13,7 @@ font-family: monospace; font-size: smaller;" width="100">
|
||||
|
||||
|
||||
$ ./busybox
|
||||
BusyBox v1.00 (2004.04.06-14:56+0000) multi-call binary
|
||||
BusyBox v1.00 (2004.10.13-04:49+0000) multi-call binary
|
||||
|
||||
Usage: busybox [function] [arguments]...
|
||||
or: [function] [arguments]...
|
||||
|
||||
@ -22,9 +22,13 @@ companies listed below should be ashamed of themselves. Furthermore, each
|
||||
product listed here is subject to being legally ordered to cease and desist
|
||||
distribution for violation of copyright law, and the distributor of each
|
||||
product is subject to being sued for statutory copyright infringement damages
|
||||
plus legal fees. Nobody wants to be sued, and <a
|
||||
href="mailto:andersen@codepoet.org">Erik</a> certainly has better things to do
|
||||
than sue people. But he will sue if forced to do so to maintain compliance.
|
||||
of up to $150,000 per work plus legal fees. Nobody wants to be sued, and <a
|
||||
href="mailto:andersen@codepoet.org">Erik</a> certainly would prefer to spend
|
||||
his time doing better things than sue people. But he will sue if forced to
|
||||
do so to maintain compliance.
|
||||
|
||||
<p>
|
||||
|
||||
Do everyone a favor and don't break the law -- if you use busybox, comply with
|
||||
the busybox license by releasing the source code with your product.
|
||||
|
||||
@ -32,7 +36,6 @@ the busybox license by releasing the source code with your product.
|
||||
|
||||
<ul>
|
||||
|
||||
<li><a href="http://www.dlink.com/"> DLink - Model GSL-G604T, DSL-300T, and possibly other models</a>
|
||||
<li><a href="http://www.trittontechnologies.com/products.html">Tritton Technologies NAS120</a>
|
||||
<br>see <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0404.0/1611.html">here for details</a>
|
||||
<li><a href="http://www.macsense.com/product/homepod/">Macsense HomePod</a>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user