All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Poole <mdpoole@troilus.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: =?iso-8859-1?q? Raphaël Rigo LKML?= <lkml@twilight-hall.net>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	davids@webmaster.com,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Dmitry Torokhov" <dtor_core@ameritech.net>
Subject: Re: GPL Violation of 'sveasoft' with GPL Linux Kernel/Busybox +code
Date: 09 Nov 2004 23:14:55 -0500	[thread overview]
Message-ID: <87actqfigw.fsf@sanosuke.troilus.org> (raw)
In-Reply-To: <053C3394-32C5-11D9-857E-000393ACC76E@mac.com>

Kyle Moffett writes:

> > 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.

> > Only your contract entitles you to that support, and if you do
> > something to terminate your contract, it is outside the GPL's scope.
> What _is_ inside the GPL's scope is that no contract may require me
> to abstain from my GPL rights.  If I use my full GPL rights, then they
> are telling me that I break the contract and lose my $20 support.

That depends greatly on the wording of the contract.

Interestingly, the only description I can find on Sveasoft's web page
says this:

    Sveasoft firmware and support is available for a yearly $20 USD
    subscription fee. A subscription includes unlimited access to
    firmware upgrades and unlimited access to priority support.

If Sveasoft terminates someone's "unlimited" access before the year
expires, Sveasoft may be in breach of contract, since there are no
disclaimers about termination -- but that still does not translate to
copyright infringement.

> > This is unpleasant for a lot of people.  It is probably suboptimal for
> > the free software community.  Life can be hard like that.  Any
> > competent lawyer could have a copyright infringement claim dismissed
> > if the claim were based on your theory of the GPL.
> As I said, IANAL, but I do feel strongly about this issue (though I've
> never paid for their software).  In any case, I think this point will be
> moot if SveaSoft continues with their announced plan to require an
> activation key.  That would _definitely_ be against the GPL.

I suspect that an activation key would violate the GPL, but that is a
different question than the support contract.

Michael Poole

  reply	other threads:[~2004-11-10  4:15 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 [this message]
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
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=87actqfigw.fsf@sanosuke.troilus.org \
    --to=mdpoole@troilus.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davids@webmaster.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@twilight-hall.net \
    --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 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.