public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: Kernl module ethics.
@ 2002-02-28 18:25 Jeffrey W. Baker
  2002-02-28 18:55 ` Jeff V. Merkey
  0 siblings, 1 reply; 3+ messages in thread
From: Jeffrey W. Baker @ 2002-02-28 18:25 UTC (permalink / raw)
  To: Jeff V. Merkey; +Cc: linux-kernel


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.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Kernl module ethics.
  2002-02-28 18:25 Kernl module ethics Jeffrey W. Baker
@ 2002-02-28 18:55 ` Jeff V. Merkey
  2002-02-28 22:16   ` Stephen Samuel
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff V. Merkey @ 2002-02-28 18:55 UTC (permalink / raw)
  To: Jeffrey W. Baker; +Cc: linux-kernel

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Kernl module ethics.
  2002-02-28 18:55 ` Jeff V. Merkey
@ 2002-02-28 22:16   ` Stephen Samuel
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Samuel @ 2002-02-28 22:16 UTC (permalink / raw)
  To: Jeff V. Merkey; +Cc: Jeffrey W. Baker, linux-kernel

As I remember it (I haven't watched changes in the legislation),
the UCTIA also had language to the effect that license terms that
require the release of derivative software are not valid.

In other words, this UCTIA language actually tries to rip the THROAT
out of the GPL... reducing it to, at best, a BSD-like license.

   (IANAL)

The theory of the GPL is that it's not actually a license. It
gives permission for people to do things with the code that would,
otherwise, be a breach of copyright unless such actions included
making the source code available to anybody that got a binary
copy of the package.

Under that premise, a GPL violation would simply be a copyright
violation case... "

IF You don't make the source code available and copyable
THEN
	You don't have the right to distribute copies of our code
FI

If this is accurate, it's possible that the GPL may actually
dodge the bullet on the UCTIA language.... but - once again - IANAL.

Jeff V. Merkey wrote:
> 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 

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

> 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.
-- 
Stephen Samuel +1(604)876-0426                samuel@bcgreen.com
		   http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-02-28 22:24 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-28 18:25 Kernl module ethics Jeffrey W. Baker
2002-02-28 18:55 ` Jeff V. Merkey
2002-02-28 22:16   ` Stephen Samuel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox