public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Michon <pierre@no-spam.org>
To: linux-kernel@vger.kernel.org
Subject: Re: freebox possible GPL violation
Date: Thu, 6 Oct 2005 14:01:35 +0200	[thread overview]
Message-ID: <20051006120135.GA1002@linux.ensimag.fr> (raw)

Hi,

>I might have misunderstood but I think that if you buy the hardware you
>cannot connect it to the DSLAM network anymore. So that only the boxes
>they own are connected to the DSLAM.

Again have you any proof that there aren't any Linux firmware in the
flash of the freebox ?
How do you explain that the boot sequence isn't stateless ?
Why in case of a firmware update, you have a special state of 10 seconds
were the freebox seem to download and write some data somewhere ?

So yes may be you can't connect anymore to the free DSLAM, but there is
may be still GPL data in the flash.

>Are you sure this point has been clarified in court in the past ?
>If not, I would bet on it (for the specific case of settop boxes).

For french law I don't know, but someone on gpl-violation this is true
for de and au.

>I mentioned in another mail the case of a mobile phone network
>infrastructure where the network nodes to which mobile phones are
>connecting are running Linux. It seems to be an "internal use" (as it
>never leak out of the company network) and yet providing a service to
>customers.

No the freebox is more like a dvb box that is lended by a satellite
provider and could do firmware update via satellite.

I don't know if there are similar case for dvb box.


Pierre

             reply	other threads:[~2005-10-06 12:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 12:01 Pierre Michon [this message]
2005-10-06 13:06 ` freebox possible GPL violation Emmanuel Fleury
2005-10-06 13:40   ` Michael Poole
2005-10-06 14:48     ` Matan Peled
  -- strict thread matches above, loose matches on Subject: below --
2005-10-06 23:26 Pierre Michon
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 11:13 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
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
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=20051006120135.GA1002@linux.ensimag.fr \
    --to=pierre@no-spam.org \
    --cc=4344F39B.10806@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