From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Andrew Miklas <public@mikl.as>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linksys WRT54G and the GPL
Date: 08 Jun 2003 15:23:00 +0100 [thread overview]
Message-ID: <1055082180.29154.0.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030608115402.GA19307@suse.de>
On Sul, 2003-06-08 at 12:54, Dave Jones wrote:
> Curiously, the Belkin products (http://networking.belkin.com) also seem
> to be based upon the same source. Looks like they could just be
> rebranded firmware images with some features disabled.
If Belkin are shipping the same code and apparently got it from Linksys
someone migth also care to write to Belkin and inform them about this.
They may not even know about their rather large potential liability.
next prev parent reply other threads:[~2003-06-08 14:11 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 2:41 Linksys WRT54G and the GPL Andrew Miklas
2003-06-08 11:54 ` Dave Jones
2003-06-08 14:23 ` Alan Cox [this message]
2003-06-08 18:13 ` uaca
2003-06-08 19:44 ` Colm MacCárthaigh
2003-06-08 20:14 ` Jörn Engel
2003-06-08 21:47 ` Russell King
2003-06-09 22:37 ` Daniel Phillips
2003-06-10 22:47 ` Andrew Miklas
2003-06-11 12:42 ` Alan Cox
2003-06-11 14:28 ` Kent Borg
2003-06-09 5:22 ` Frank Cusack
[not found] ` <20030609053010$504e@gated-at.bofh.it>
2003-06-09 8:28 ` Florian Weimer
2003-06-09 14:09 ` Horst von Brand
2003-06-09 18:23 ` Alan Cox
2003-06-09 21:33 ` Adrian Bunk
2003-06-09 21:50 ` David Schwartz
2003-06-09 22:21 ` Adrian Bunk
2003-06-10 20:17 ` Randolph Bentson
2003-06-11 15:38 ` Adrian Bunk
2003-06-11 17:39 ` Randolph Bentson
2003-06-11 19:22 ` Adrian Bunk
2003-06-11 20:12 ` David Schwartz
2003-06-11 20:31 ` "any third party" (Re: Linksys WRT54G and the GPL) Filip Van Raemdonck
2003-06-11 20:51 ` Eli Carter
2003-06-09 5:32 ` Linksys WRT54G and the GPL David Schwartz
2003-06-09 5:47 ` Frank Cusack
2003-06-09 16:53 ` David Schwartz
2003-06-09 18:25 ` Alan Cox
2003-06-09 21:37 ` Adrian Bunk
2003-06-08 3:13 Brad Chapman
2003-06-08 16:35 ` Davide Libenzi
2003-06-08 3:53 Erik Andersen
2003-06-08 10:08 ` Henning P. Schmiedehausen
2003-06-08 12:01 ` Christian Ullrich
2003-06-08 13:52 ` Dr. David Alan Gilbert
2003-06-08 14:05 ` Marcus Metzler
2003-06-08 16:49 ` Adrian Bunk
2003-06-08 17:00 ` Dr. David Alan Gilbert
2003-06-08 20:41 greendisease
2003-06-08 21:08 ` Davide Libenzi
2003-06-08 21:23 ` Jack Aboutboul
2003-06-08 21:50 ` Russell King
2003-06-08 22:48 ` Davide Libenzi
2003-06-08 20:57 Peter Westwood
2003-06-08 21:52 ` Russell King
2003-06-08 23:18 ` bill-linuxkernel20030609
2003-06-09 0:19 ` Oliver M. Bolzer
2003-06-09 0:31 ` Jeff
2003-06-10 20:43 ` Michael Neuffer
2003-06-08 23:25 Hakan Lennestal
2003-06-08 23:55 ` Martin List-Petersen
2003-06-09 8:47 ` Hakan Lennestal
2003-06-08 23:35 Erik Andersen
2003-06-09 0:09 ` Paul Jakma
2003-06-09 1:11 ` Erik Andersen
2003-06-09 0:05 Erik Andersen
2003-06-09 3:39 ` John Shifflett
2003-06-09 18:26 ` Alan Cox
2003-06-09 3:47 Russ Dill
2003-06-09 8:04 ` Russell King
2003-06-09 13:13 Downing, Thomas
2003-06-09 16:49 ` Martin List-Petersen
2003-06-10 4:11 Russ Dill
2003-07-18 23:48 root
2021-01-17 17:51 nipponmail
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=1055082180.29154.0.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=public@mikl.as \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.