mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernl module ethics.
Date: Thu, 28 Feb 2002 11:55:58 -0700	[thread overview]
Message-ID: <20020228115558.A5435@vger.timpanogas.org> (raw)
In-Reply-To: <1014920752.21006.17.camel@heat>
In-Reply-To: <1014920752.21006.17.camel@heat>; from jwbaker@acm.org on Thu, Feb 28, 2002 at 10:25:36AM -0800

On Thu, Feb 28, 2002 at 10:25:36AM -0800, Jeffrey W. Baker wrote:
> 
> On Thu, Feb 28, 2002, Jeff V. Merkey wrote:
> 
> >There is a belief that the GPL can contaminate upward and 
> >downward any driver or kernel module written that runs on Linux.
> >This statement, irregardless of what language is in the GPL, is
> >total bullsh_t, **EXCEPT** in those states who have adopted 
> >UCITA.   UCITA is an evil body of legislation approved by 
> >representatives of various state legislatures that in essence 
> >makes anything written into a software license (like the GPL) 
> >enforceable and potentially criminal in those states who adopt
> >UCITA for any use of a particular software program.  By way of 
> >example, UCITA makes reverse engineering an illegal act if 
> >the software owner writes into the license that reverse engineering
> >is not allowed.   UCITA will also give the GPL enormous "teeth"
> >to actually enforce this up/down contamination of code written 
> >on the Linux kernel.  
> 
> Jeff, you are WAY off in left field.  The GPL is fundamentally different
> from any other software license.  The so-called license that comes with
> Windows seeks to limit the rights of the Windows buyer.  It limits your
> right to fair use, criticism, and so forth.  The GPL is different
> because it actually grants you rights you would not have other wise had:
> the right to redistribute the software product.
> 
> UCITA seeks to make Microsoft's license -- which cannot be a contract
> because it provides no benefit for the software user and no obligation
> for the software maker -- enforceable as a contract.  Again the GPL is
> fundamentally different because people assent to its terms for their own
> benefit.  Microsoft's license provides no benefit and no person would
> ever agree to it, nor do they need to: their rights are secured as the
> buyer of goods[1] and they can throw the license in the recycling pile.
> 
> -jwb
> 
> 1: "The Court understands fully why licensing has many advantages for
> software publishers. However, this preference does not alter the Court's
> analysis that the substance of the transaction at issue here is a sale
> and not a license."  Judge Dean D. Pregerson, United States District
> Court for the Central District of California.
> 

The GPL could be enforced under UCITA.  Whether someone would succeed 
or not is another matter, but a claim could be brought.  The GPL is 
a "contract" and it's not "fundamentally different" in any significant
way from any other software license.  It defines how someone may use 
software and what obligations they have.  In fact, it's exactly the 
type of contract UCITA addresses.  disagree.

:-)

Jeff



  reply	other threads:[~2002-02-28 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 18:25 Jeffrey W. Baker
2002-02-28 18:55 ` Jeff V. Merkey [this message]
2002-02-28 22:16   ` Stephen Samuel

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=20020228115558.A5435@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=jwbaker@acm.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®