public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Aiko Barz <aiko@chroot.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: WRT54G
Date: Mon, 20 Sep 2004 14:13:42 +0100	[thread overview]
Message-ID: <1095686020.26647.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20040919095857.GD17602@lain.chroot.de>

On Sul, 2004-09-19 at 10:58, Aiko Barz wrote:
> Hi there!
> 
> It's the wrt54g subject again...
> I'm mirroring the Sveasoft-firmware, which was published under the
> terms of "GPL". At least Sveasoft said that. 

Can you prove they said that ?

> This site http://www.linksys.com/support/gpl.asp also implies, that i
> can redistribute those drivers and firmwares. But it is the same
> problem with them. Those wrt54g-firmwares also contain non-GPL
> sourcecodes and binaries.

It's up to Linksys what license they grant you for their non-free stuff.
If its linked with GPL stuff then it might be GPL because its a
derivative work. Sveasoft's only business is code they own the copyright
to themselves and didn't give other people rights to redistribute (or
gave them specifically revokable rights to distribute)

> Sveasoft is hunting down mirrorsites right now. Of course, they want
> to earn some money. So i'm not sure what I should do next?!
> Going down or asking for the rest of the code?

That depends what they said about the code and what you can prove about
it. Sveasoft's evil claws extend only to code they themselves own
copyright to and have not already granted things like GPL rights too (or
any other irrevocable right). 

It highlights the dangers of relying on a partially proprietary software
stack, as well as why Richard Stallman always asks vendors of Linux and
other free software products that if they also bundle non-free software
it is easy to tell which is which. Hence Debian has a seperate non-free
archive, Fedora is open source only but there are third party yum
repositories for non-free products and so on.

Alan


  reply	other threads:[~2004-09-20 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19  9:58 WRT54G Aiko Barz
2004-09-20 13:13 ` Alan Cox [this message]
2004-09-21 12:10   ` WRT54G Daniel Egger
  -- strict thread matches above, loose matches on Subject: below --
2004-09-22  7:41 WRT54G www.sveasoft.com
2004-09-22  9:55 ` WRT54G Daniel Egger
2004-09-22 14:08 ` WRT54G Alan Cox

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=1095686020.26647.10.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=aiko@chroot.de \
    --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