From: vanstadentenbrink@ahcfaust.nl
To: linux-kernel@vger.kernel.org
Subject: RE: GPL violations by wireless manufacturers
Date: Tue, 24 Jun 2003 13:20:36 +0200 [thread overview]
Message-ID: <3EF85024.4477.78EB14@localhost> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKKEEDDOAA.davids@webmaster.com>
[ Please CC replies as I am not subscribed ]
In response to DS:
> So is a Linux distribution "a whole which is a work based on the" Linux
> kernel? Would you argue that RedHat can't include proprietary software on
> the same CD as the Linux kernel? All the software on the CD, assuming it's
> Linux software, likewise extends the kernel through a well-defined boundary.
No, definitely not. If that were the case, SuSE and Lindows etc. etc.
would not be able to distribute proprietary software together with
GPL'ed software. The GPL calls this 'mere aggregation':
"In addition, mere aggregation of another work not based on the
Program with the Program (or with a work based on the Program) on a
volume of a storage or distribution medium does not bring the other
work under the scope of this License."
These wireless products are different. The user doesn't have a choice
to use or not to use the non-gpl'ed kernel module. He can not prevent
the module from loading, he can not remove it from the running kernel
and the device doesn't operate without the module. The module and the
embedded Linux OS on the device are so interconnected that they can
not be considered 'seperate works' under the GPL. Therefore the
kernel module actually is GPL software itself.
Buffalo Technology's response indicates that they agree with me (or
perhaps they just don't want any trouble).
In response to Zack Gilburd:
> ...But where are the downloads? :-\
They don't have to offer the source as a download under the GPL. They
just have to enable you to get to the source. As soon as Buffalo puts
on the their website that they use GPL'ed software (they said they
would do that within 48 hours) you should be able to request and
receive the source code of the embedded Linux OS as well as the
source code of the kernel module.
Richard Ten Brink
next prev parent reply other threads:[~2003-06-24 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 10:10 GPL violations by wireless manufacturers vanstadentenbrink
2003-06-24 10:38 ` David Schwartz
2003-06-24 11:20 ` vanstadentenbrink [this message]
2003-06-24 18:18 ` David Schwartz
2003-06-24 23:37 ` vanstadentenbrink
2003-06-25 2:42 ` Horst von Brand
2003-06-29 3:14 ` Andre Hedrick
2003-06-24 18:25 ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Roger Larsson
2003-06-24 23:26 ` Krzysztof Halasa
2003-06-25 0:27 ` Zack Gilburd
2003-06-25 0:39 ` Bryan Andersen
2003-06-25 0:41 ` developers and GPL in products (Was: Re: GPL violations by wi reless manufacturers) David Lang
2003-06-25 0:47 ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Robins Tharakan
2003-06-25 3:21 ` Brian Davids
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 18:53 GPL violations by wireless manufacturers Andrew Miklas
[not found] <20030628151540.A16039@mn.rr.com>
2003-06-29 21:22 ` vanstadentenbrink
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=3EF85024.4477.78EB14@localhost \
--to=vanstadentenbrink@ahcfaust.nl \
--cc=linux-kernel@vger.kernel.org \
/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