Gpl compliance letter

MAIL1

Hello,

My name is [Name] [Surname]. I am a developer and interested in FOSS (free
and
open source software).

I am writing with regards to one of your products XYZ. From the official KB
documentation
(XYZ_Admin.pdf) and practical examples from my fellow
developers/users and my own experience with the product, I came to know that
you are using a (possibly modified)
Linux-kernel.

Since Linux is licensed under GPL (http://www.linux.org/info/gnu.html), I
would like to kindly ask for a location/way to view the source files used
for
building the kernel of the "SecureJet Box" product as well as full/detailed
build instructions and any other dependent software used in connection to
building this kernel.

Please treat this request as important as possible. Also, if required or my
request is not fully understood, I can assist you with any information
required from my side. As well, you can check GPL-related policies and
requirements with your legal consultants.

Looking forward for your reply.

Thanks a lot.
[Name] [Surname]

============================================================================
=============

REPLY1

Dear Sir,

Thank you for your inquiry.
Our company is using a standard BUILDROOT environment
(http://buildroot.uclibc.org/) to produce the SecureJet Box 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.

Sincerely,
Vendor1

============================================================================
=============

Dear Vendor1 team,

First, thanks for you previous fast reply.

However, I would insist on my initial points.

According to Chapter3 of GPLv2:
"The source code for a work means the preferred form of the work for making
modifications to it. For an executable work, complete source code means all
the source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and
installation of the executable."

Since buildroot is a set of "scripts used to control compilation of the
executable", the exact scripts used for the product must be supplied. It is
also necessary to provide under the license agreement "scripts (source code)
used for installation of the executable".

Also, I could not find any reference on your site nor in the
brochures/documentation the GPL license agreement. According to Chapter1 of
GPLv2:
"You may copy and distribute verbatim copies of the Program's source code as
you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
License and to the absence of any warranty; and give any other recipients of
the Program a copy of this License along with the Program"

For more information, I would be glad to suggest GPL license according to
points mentioned above and GPL-Violations organization FAQ:
http://gpl-violations.org/faq/sourcecode-faq.html
http://www.gnu.org/licenses/gpl2.html

Also, members of GPL-violations (http://gpl-violations.org/) would be more
than happy to clarify any of the GPL terms in case of doubts.

Looking forward for your reply.

Thanks a lot

Regards,
[Name] [Surname]