From: Helge Hafting <helge.hafting@aitel.hist.no>
To: David Lang <david.lang@digitalinsight.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
Emmanuel Fleury <fleury@cs.aau.dk>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: freebox possible GPL violation
Date: Thu, 06 Oct 2005 11:20:36 +0200 [thread overview]
Message-ID: <4344EC64.2010400@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.62.0510051741310.14560@qynat.qvtvafvgr.pbz>
David Lang wrote:
> On Thu, 6 Oct 2005, Helge Hafting wrote:
>
>> If the box downloads a linux kernel through the DSLAM network, then
>> someone is clearly distributing linux kernels through the DSLAM network.
>> I would guess it is the same guys, because relying on someone else
>> providing
>> them with kernels is a risky business. But whoever is on the other end
>> of the DSLAM net have to offer the source as well, because they _are_
>> distributing kernels.
>>
>> The fact that the user isn't supposed to know how this box work
>> doesn't change anything, of course. The GPL says those who
>> distribute the work - it doesn't matter that they don't tell the
>> customer that they're given a linux kernel. They still have to offer
>> the source if asked.
>
>
> the argument that they are making is that they are only moveing the
> kernel within their own companies equipment, and therefor it doesn't
> count as 'distribution'
Interesting argument, but it breaks for at least two reasons:
1. You can buy that box instead of just hiring it. That moves kernels
"outside the company",
for money even.
2. It doesn't matter if they only move kernels withing their own
companys equipment.
If they lend a customer equipment containing a linux kernel, then
they're lending
them a linux kernel. Lending is distribution!
>
> agree with this argument or not, but please acknowledge this point of
> view rather then pretending that they have no argument at all and are
> just plain refusing.
The argument might be fine, if they were moving linux kernels into
company equipment
used by company personell only. (I.e. linux-powered
desktops/servers/gadgets for their employees.)
And it might not. Maybe they actually have to distribute source to
employees too, if they
request it. The GPL only mentions recipients, no exceptions for
"internal company use". A company
may perhaps demand that the employees never request the source, though.
Or perhaps
"internal use" is covered by the company being a "legal unit".
People breaking the GPL should be taken seriously. Fortunately, the
solution is easy for
GPL-breakers. Break someone else's license, and they have to pay
damages. Break the GPL,
and all you need to do is to stuff some source code onto a public
(web/ftp)server - and all is fine again.
The situation is so cheap and _easy_ to rectify, that is one reason
people gets so pissed off at
a violation. It is not as if complying with the GPL would be any kind
of burden to them.
Helge Hafting
next prev parent reply other threads:[~2005-10-06 9:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:13 freebox possible GPL violation Pierre Michon
2005-10-05 11:22 ` Emmanuel Fleury
2005-10-05 11:27 ` Arjan van de Ven
2005-10-05 11:37 ` Emmanuel Fleury
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 12:02 ` Emmanuel Fleury
2005-10-05 12:07 ` Arjan van de Ven
2005-10-05 12:29 ` Emmanuel Fleury
2005-10-05 12:45 ` Michael Poole
2005-10-05 17:11 ` Alexandre Oliva
2005-10-06 0:07 ` Helge Hafting
2005-10-06 0:49 ` David Lang
2005-10-06 1:12 ` Stefan Smietanowski
2005-10-06 2:25 ` David Lang
2005-10-06 9:20 ` Helge Hafting [this message]
2005-10-06 9:51 ` Emmanuel Fleury
2005-10-06 9:53 ` Emmanuel Fleury
2005-10-06 11:39 ` Helge Hafting
2005-10-06 13:05 ` Emmanuel Fleury
2005-10-06 13:42 ` Michael Poole
2005-10-06 14:19 ` Helge Hafting
2005-10-06 20:15 ` Stefan Smietanowski
2005-10-11 2:27 ` David Schwartz
2005-10-11 10:48 ` Graham Murray
2005-10-05 12:15 ` Vincent Hanquez
2005-10-05 11:45 ` linux-os (Dick Johnson)
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 11:50 ` Emmanuel Fleury
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 23:26 Pierre Michon
2005-10-06 12:01 Pierre Michon
2005-10-06 13:06 ` Emmanuel Fleury
2005-10-06 13:40 ` Michael Poole
2005-10-06 14:48 ` Matan Peled
2005-10-05 17:57 Pierre Michon
2005-10-05 16:06 Pierre Michon
2005-10-05 16:47 ` Emmanuel Fleury
2005-10-05 15:18 Pierre Michon
2005-10-05 15:49 ` Vincent Hanquez
2005-10-05 15:12 Pierre Michon
2005-10-05 15:08 Pierre Michon
2005-10-05 10:08 Pierre Michon
2005-10-05 10:18 ` Emmanuel Fleury
2005-10-05 8:47 Pierre Michon
2005-10-05 9:42 ` Helge Hafting
2005-10-15 9:40 ` Loic Dachary
2005-10-19 17:58 ` Pierre Michon
2005-10-20 15:29 ` Loic Dachary
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=4344EC64.2010400@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=arjan@infradead.org \
--cc=david.lang@digitalinsight.com \
--cc=fleury@cs.aau.dk \
--cc=helgehaf@aitel.hist.no \
--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