Busybox Comply

[Denys Vlasenko]

On Wednesday 28 November 2007 10:58, Guilherme wrote:
>  Dear Denis,
>
>  I'm writing to tell you guys that we are working with this products: Model
> AP Router WR 254 and AP Router WR 252
> http://www.aprouter.com.br/wireless_content/aprouter_wr254_access_point_wir
>eless_router.html
> http://www.aprouter.com.br/wireless_content/produtos_wireless_ap_router_wr2
>52.html
>
>
>  This product have a  firmware which uses your Busybox code.
>  I would like to send to you the source code link:
> http://www.aprouter.com.br/firmware/firmware-source.zip  and gently ask
> your permission to keep working with this product.

Sure. If I underrstand it right, here is what you need to do
in order to comply with the license:

You need to make your source available to users.
I guess keeping in on company's website is simplest solution.
Just don't forget to update firmware source tarball on the site
when you deploy new version.

The tarball should not be concealed somewhere deep inside
the site, it should be easy for users to find.

Add an instruction how they can build this source.

You are not required to provide a way to build it with freely
available toolchain (it is okay if you build it with some
commercial compiler), but at least mentioning which compiler
is known to build it properly, and what command line options
need to be given to it, build scripts, etc, is required.

It's legally ok if you don't provide any support for users
which run firmware built from source. 

You are also not required to provide for means of downloading
user-built firmware into the device.
--
vda