From: Stephen Samuel <samuel@bcgreen.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernl module ethics.
Date: Thu, 28 Feb 2002 14:16:58 -0800 [thread overview]
Message-ID: <3C7EAC5A.1050108@bcgreen.com> (raw)
In-Reply-To: <1014920752.21006.17.camel@heat> <20020228115558.A5435@vger.timpanogas.org>
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.
prev parent reply other threads:[~2002-02-28 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=3C7EAC5A.1050108@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=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