public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Gregory Maxwell <greg@linuxpower.cx>,
	Mark Spencer <markster@linux-support.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.0-test9 not Open Source
Date: Sat, 28 Oct 2000 13:57:54 -0600	[thread overview]
Message-ID: <39FB2FC2.28572A70@timpanogas.org> (raw)
In-Reply-To: <E13pZq3-0005TZ-00@the-village.bc.nu>



Alan Cox wrote:
> 
> > In this case, Debian (or any organization who isn't big enough not to fear
> > M-systems) may not ship the standard kernel because it has additional patent
> > restrictions.
> 
> Why. There are no distribution restrictions
> 
> > There is a clear ability here for the author of the driver and m-systems to
> > conspire to retroactively revoke anyones privilege to use, modify, or
> > distribute the stock kernel because of this code.
> 
> I fail to see how
> 


Alan is right.  The way it's worded, they could never show a case for
"irreparable harm" to any sitting judge in the US.   This means they
could say "we've changed our minds, and revoke this persons or that
person's license" but given it's been released with this language, no
case for harm or damages, or even a petition for injunctive relief would
have a snowball's change in hell of succeeding.  

If you release code under the GPL, you basically waive any rights to
seek enforcement because in the US, you must be able to show
"irreparable harm" from some parties use of the code.  It's tough to do
this if you've given the code away (which the GPL does) without a
contractural requirement for "consideration" ($$$).  The GPL in the
strictest legal sense is the ultimate IP legal virus because it not only
removes the basis for damages claims for use of present code released
under it's terms, but since it covers derivative works, it's effect
contaminates all future incarnations of the code.

It's true with how this is worded, the party could come back and attempt
to modify the scope, but they would be hard pressed to make a case for
an injunction to halt someone's use of the code.

:-)

Jeff



> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-28 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-28 16:02 Linux-2.4.0-test9 not Open Source Mark Spencer
2000-10-28 16:24 ` Alan Cox
2000-10-28 17:24   ` Gregory Maxwell
2000-10-28 17:32     ` Alan Cox
2000-10-28 19:57       ` Jeff V. Merkey [this message]
2000-10-30 17:01     ` David Woodhouse
2000-10-30 18:27       ` Alan Cox
2000-10-30 16:45 ` 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=39FB2FC2.28572A70@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@linuxpower.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markster@linux-support.net \
    /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