From: Andrei Costin (lists) <lists@andreicostin.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot GPL question
Date: Mon, 31 May 2010 20:49:56 +0300 [thread overview]
Message-ID: <002f01cb00e9$af8f1180$0ead3480$@com> (raw)
Hi,
I would like someone's advise for the course of action regarding a vendor
that used _buildroot_ to compile an embedded linux kernel for their
hardware product.
I have contacted them, and their response is below:
"Thank you for your inquiry.
Our company is using a standard BUILDROOT environment
(http://buildroot.uclibc.org/) to produce the product.
No modifications were made on original 2.6 kernel and other applications
under the GPL licence.
therefore we recommend you connect to http://buildroot.uclibc.org to get all
extra information."
Also, their product documentation and license doesn't mention at all GPL
license in relation to the linux kernel (and other stuff used).
So, given a hardware unit with embedded linux kernel built with _buildroot_,
what exact things does vendor have to provide:
- In terms of documentation/license text?
- In terms of source code and build environment (build and install
scripts/steps)
My assumptions are:
- Documentation should mention the GPL license and the exact GPL
modules used. Also, documentation should state how to get the necessary
source code/configuration (FTP link, mailing address for CD order, etc.)
- Source code (exact source tree or reference to an exact
version/revision) as well as exact configuration/makefiles used for building
the embedded environment (including configuration files for their buildroot
development environment)
Any advise is highly appreciated.
Thanks a lot
Kind regards,
Andrei Costin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100531/3ea62ad2/attachment.html>
next reply other threads:[~2010-05-31 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 17:49 Andrei Costin [this message]
2010-05-31 18:54 ` [Buildroot] buildroot GPL question Michael S. Zick
2010-05-31 19:12 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002f01cb00e9$af8f1180$0ead3480$@com' \
--to=lists@andreicostin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox