mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr@rogers.com>
To: license-violation@fsf.org
Cc: license-violation@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: [gnu.org #214016] GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code
Date: Tue, 9 Nov 2004 10:20:52 -0500	[thread overview]
Message-ID: <200411091020.52578.shawn.starr@rogers.com> (raw)
In-Reply-To: <rt-3.0.8-214016-682805.9.72099995582191@rt.gnu.org>

They won't be distributing the source because of their new 
anti-distribution methods, they aren't providing the source because they 
don't want people to distribute the binaries any more either or know now the 
anti-distribution mechanism will work (which requires the user to enter a 
value to unlock the binary firmware and send a request to their servers).

It is this action that they are violating the GPL and that needs to be 
enforced. 

If they want to relicense their changes they need to not use GPL existing code 
which they are not doing. They have not added written any of this code from 
scratch and thus must distribute the source on request to those who get the 
binaries which they are not doing anymore.

What was true before of redistribution and being kicked out of the program is 
now not happening anymore as there is no code to distribute of the resulting 
binaries.

Shawn.

On November 9, 2004 07:07, Alan Cox via RT wrote:
> On Maw, 2004-11-09 at 00:11, novalis@fsf.org via RT wrote:
> > But if you distribute binaries, you must either include or offer source
> > code.  Do they do this?  What software do they include that FSF holds
> > copyright on?   Where can I check this?
> >
> > Do they include a copy of the GPL with the software?
>
> They include the GPL, they include the source nothing I can find they do
> violates the GPL.  They do appear to annoy a few people because their
> policy is that while you may join their early access process and get
> source if you redistribute that source then you get kicked off their
> program, but you are still allowed to distribute that source.

  reply	other threads:[~2004-11-09 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rt-214016@gnu.org>
2004-11-09  0:11 ` novalis@fsf.org via RT
2004-11-09 12:07 ` Alan Cox via RT
2004-11-09 15:20   ` Shawn Starr [this message]
2004-11-09 15:21 ` Shawn Starr via RT
2004-11-09 15:28 ` Shawn Starr via RT
2004-11-11  0:23 ` novalis@fsf.org via RT

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=200411091020.52578.shawn.starr@rogers.com \
    --to=shawn.starr@rogers.com \
    --cc=license-violation@fsf.org \
    --cc=license-violation@gnu.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

all inboxes | Powered by JetHome®