public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Michon <pierreno-spam!org@ensilinx1.imag.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: freebox possible GPL violation
Date: Wed, 5 Oct 2005 17:18:46 +0200	[thread overview]
Message-ID: <20051005151846.GA760@linux.ensimag.fr> (raw)

Hi,

>The bottom line is the Freebox is still owned by Free when you are using
>it. It you "buy" it (by not giving it back and paying 400 EUR), you
>don't have the right anymore to plug it into free network, thus don't
>have access to freebox's firmware.
So how do you explain my point B ?

Why does it need to reboot when there is a new firmware ?

How they manage to download the firmware (need led driver, ppp, http,
adsl driver, atm stack, ...)

>but please keep that away from the LKML, this is *offtopic* here.
>This list is about *developement* of the linux kernel..
Please suggest other mailling lists.


Pierre

             reply	other threads:[~2005-10-05 15:18 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 15:18 Pierre Michon [this message]
2005-10-05 15:49 ` freebox possible GPL violation Vincent Hanquez
  -- 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: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=20051005151846.GA760@linux.ensimag.fr \
    --to=pierreno-spam!org@ensilinx1.imag.fr \
    --cc=20051005121542.GA13284@snarc.org \
    --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