public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Fleury <fleury@cs.aau.dk>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: freebox possible GPL violation
Date: Thu, 06 Oct 2005 15:05:56 +0200	[thread overview]
Message-ID: <43452134.4010504@cs.aau.dk> (raw)
In-Reply-To: <43450CE5.50302@aitel.hist.no>

Helge Hafting wrote:
>
> Well, but there still is a kernel in the box that was downloaded before
> they bought it?  Or does the box become unuseable when they buy it?

No idea, I don't have a Freebox yet.

> If I make a business out of lending windows boxes, then I have to pay
> licences
> on each box.  If I lend customers linux boxes, I should lend them the
> source too if they
> requests it.  Remember, even if the average customer doesn't know what
> software
> is in the box, they still have the right to make a copy of the linux
> kernel, because you
> cannot take away that right.

You got an extremely good point here. At least it shows why this way of
doing is not "moral", but, looking at the GPL text, there is nothing
stating any obligation to "pay" in any manner (money or contributions)
to use and/or modify GPLed softwares.

Just to illustrate my point, in the case of an webserver, if the
webmaster patch the code of his own webserver to provides his customers
with a new service. Has he the obligation to redistribute this code ?
Namely, his patched webserver will never get distributed. The only
interaction between the customers and his webserver will be through
exchanges of HTML files.

And anyway, to whom redistribute the code ? Indeed, what would do the
customers with such code ? As they are only using the service without
really touching the software.

Therefore, it would be nice from the webmaster to contribute with his
patch, but I do think that it is his own choice to do so.

Note: Originally, the redistribution of the code was mainly to avoid
customers or companies to get stuck with a "no more maintained"
binaries. In the case we are looking now, as the hardware is not
belonging to the customers, there is no such risk. So the protection
seems to be against something else... but what ?

> There have at least been cases where companies were selling
> linux-powered products, and were told that they had to
> provide the sources.  I don't know if any of them bothered
> going to court, simply making the source available (on a cd
> or webserver) is so much cheaper than that.

LinkSys is an example. But the customers were owning the machine with
everything in it (including the OS). Again, the clause on distributing
the sources help to not get stuck with a piece of hardware that you own
with no possibility of upgrade (remembers me the famous story of RMS and
the laser printer).

> An interesting thing about the GPL is that it talks about
> "distributing copies", not about "selling or otherwise changing ownership".
> 
> "Distributing" a linux kernel embedded in a product owned by the
> company doesn't change that.  Where the binary kernel go, the
> source should go too (if requested).
> 
> Fortunately, this licencing term is so easy to satisfy that it'd be silly
> to try to fight it. Stick the source on a webserver somewhere.  Provide
> the URL in the accompagnying paper (or a README file if appropriate.)
> If distributing cd's, consider sticking a tarball there.

Well, I'm really sorry to play the Devil Advocate once time more, but as
far as I know all these DSL companies have big secrets because of
weaknesses in their security. Being hacked at the Internet level is one
thing, being hacked at the DSLAM level means a lot. Try to imagine if
anybody could upload to you his own modified kernel, this means that you
can tape all the internet traffic, all the phone calls, all the TV
programs that you are looking at, and also probably having an easy way
in to your local network (wired and wifi).

Regards
-- 
Emmanuel Fleury

Live as if your were to die tomorrow.
Learn as if you were to live forever.
  -- Mahatma Gandhi

  reply	other threads:[~2005-10-06 13:07 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
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 [this message]
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=43452134.4010504@cs.aau.dk \
    --to=fleury@cs.aau.dk \
    --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