From: "David Schwartz" <davids@webmaster.com>
To: <mdpoole@troilus.org>, "Kyle Moffett" <mrmacman_g4@mac.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code
Date: Tue, 9 Nov 2004 21:07:18 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEOMPKAA.davids@webmaster.com> (raw)
In-Reply-To: <87actqfigw.fsf@sanosuke.troilus.org>
> > > You can fully exercise your rights under the GPL; they are not
> > > restricted. However, you cannot expect future support from Sveasoft.
> > But if I paid $20 for one year of said support?
> The contract might have a termination clause triggered if you do a
> handstand or file a patent lawsuit against Sveasoft. By your
> argument, that would make the contract breach the GPL, since you could
> not use the GPLed software while doing those things -- which is
> ridiculous on its face.
No, because they don't restrict your exercise of your rights under the GPL.
None of these things are predicated upon your exercise of your GPL rights,
so they don't restrict them.
If not for the GPL's further restriction clause, SveaSoft could condition
their contracts with termination clauses based upon any set of rules they
want. However, due to the GPL's further restriction clause, they cannot
penalize people for exercising their rights under the GPL. This is the
specific intent of that clause in the GPL. It's intended to prevent people's
GPL rights from being encumbered by outside licenses and contracts.
> I suspect that an activation key would violate the GPL, but that is a
> different question than the support contract.
Nope. The GPL is perfectly clear that you can modify GPL'd code to do
whatever you want. If you want to add code to require an activation key,
that is your right. If you want to distribute the resulting code, that is
your right too, assuming you comply with the GPL's other clauses. That check
on this is supposed to be that others could remove the activation key and
distribute the modified binaries and source.
SveaSoft is trying a new trick now. They're essentially claiming that their
firmware is an aggregation of both GPL'd and proprietary works, and
therefore you can't distribute it unless you can separate the works somehow.
I think they are exploiting areas of the GPL that are slightly gray.
Clearly, reasonable people can disagree on what a "further restriction" is
or what a "mere aggregation" is.
Anyway, this has long stopped being interesting to LKML folks.
DS
next prev parent reply other threads:[~2004-11-10 5:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 17:27 GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code Shawn Starr
2004-11-07 19:33 ` Raphaël Rigo LKML
2004-11-07 19:38 ` Shawn Starr
2004-11-07 21:16 ` Daniel Egger
2004-11-08 1:14 ` David Schwartz
2004-11-08 14:56 ` Pedro Venda (SYSADM)
2004-11-08 20:53 ` David Schwartz
2004-11-08 15:24 ` Alan Cox
2004-11-08 19:57 ` Geert Uytterhoeven
2004-11-08 21:33 ` Pedro Venda (SYSADM)
2004-11-08 21:54 ` David Schwartz
2004-11-08 23:25 ` Alan Cox
2004-11-08 20:53 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code David Schwartz
2004-11-08 23:00 ` Alan Cox
2004-11-09 2:32 ` Dmitry Torokhov
2004-11-09 4:08 ` David Rees
2004-11-09 4:23 ` Dmitry Torokhov
2004-11-09 9:47 ` Alan Cox
2004-11-09 19:30 ` David Schwartz
2004-11-09 19:45 ` Chris Friesen
2004-11-09 20:23 ` David Schwartz
2004-11-09 20:48 ` Valdis.Kletnieks
2004-11-09 23:06 ` Alan Cox
2004-11-10 1:47 ` David Schwartz
2004-11-10 9:27 ` Geert Uytterhoeven
2004-11-10 18:14 ` Alan Cox
2004-11-10 19:32 ` Valdis.Kletnieks
2004-11-10 20:09 ` Stuart MacDonald
2004-11-10 21:18 ` Trever L. Adams
2004-11-09 23:22 ` Alan Cox
2004-11-10 1:34 ` Kyle Moffett
2004-11-10 2:01 ` Michael Poole
2004-11-10 3:02 ` Kyle Moffett
2004-11-10 4:14 ` Michael Poole
2004-11-10 4:28 ` Dmitry Torokhov
2004-11-10 21:11 ` Bill Davidsen
2004-11-10 23:09 ` Kyle Moffett
2004-11-10 22:14 ` Alan Cox
2004-11-15 14:47 ` David Woodhouse
2004-11-10 23:26 ` Dmitry Torokhov
2004-11-10 5:07 ` David Schwartz [this message]
2004-11-10 1:47 ` David Schwartz
2004-11-12 17:04 ` Horst von Brand
2004-11-09 21:13 ` Stuart MacDonald
2004-11-09 2:23 ` GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox + code Paul Jakma
2004-11-10 10:21 ` David Woodhouse
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=MDEHLPKNGKAHNMBLJOLKMEOMPKAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdpoole@troilus.org \
--cc=mrmacman_g4@mac.com \
/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®