mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Hell.Surfers@cwctv.net>
To: davids@webmaster.com, rms@gnu.org, linux-kernel@vger.kernel.org
Subject: RE:Re: Why is Nvidia given GPL'd code to use in non-free drivers?
Date: Sun, 5 Jan 2003 05:10:02 +0000	[thread overview]
Message-ID: <048250406050513DTVMAIL4@smtp.cwctv.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

you are confusing Richard Stallman with me, I argued headers were a derivative use, this _may_ not be his view, i appologise if you feel misled.

Dean McEwan, If the drugs don't work, [sarcasm] take more...[/sarcasm].

On 	Sat, 4 Jan 2003 16:17:30 -0800 	David Schwartz <davids@webmaster.com> wrote:

[-- Attachment #2: Type: message/rfc822, Size: 4205 bytes --]

From: David Schwartz <davids@webmaster.com>
To: <rms@gnu.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Why is Nvidia given GPL'd code to use in non-free drivers?
Date: Sat, 4 Jan 2003 16:17:30 -0800
Message-ID: <20030105001731.AAA11069@shell.webmaster.com@whenever>

On Sat, 04 Jan 2003 18:44:58 -0500, Richard Stallman wrote:

>Defending shrink wrap licensing agreements, arguing to weaken
>fair use and
>first sale doctrines, and arguing that if you include a header it's
>a derived
>work is a strange way to defend intellectual freedom.

>Those are not my views.  Are you confusing me with someone else?

	Then please explain to me how the GPL comes to apply to a person who
did not agree to it as a condition of receiving a copyrighted work. 
Please explain to me why you think that the GPL should have applied 
to kernel modules that only include header files.

	You may not explicitly endorse the obvious logical consequences of 
your views, but you are still responsible for them.

>>If open source is so good, companies with closed source products
>>will
>>change.

>Yes, even without being coerced and pressured to do so by
>restrictive
>licenses.

>The Open Source Movement says that will happen; when it does, that's
>good, but if we had relied on that to give us freedom, we wouldn't
>have any free operating systems today.

	That's a lot better than trying to arm twist others in to providing 
our freedom to use their works. When you talk about forcing a person 
to distribute the source code to a derived work, you are only talking
about their control over what they added. When a person creates a 
derived work of an open source work, all they have to offer is the 
value they added. In the name of freedom, you take their control over
their work from them.

	This is the same "freedom" that socialism promises the workers. They
call it the freedom to own the machinery they use to produce. 
Analogously, this "freedom" is really just the loss of the freedom of
ownership.

>In the Free Software Movement we think freedom is worth working for.
>If companies don't choose to respect our freedom, we don't cite that
>and say "it's hopeless" and we don't say that makes non-freedom ok.
>We write free replacements and build freedom for ourselves--and for
>you.

	This is false for two reasons:

	1) The difference between the GPL and the BSD license is the GPL 
license *compels* source distribution. You can't compel someone else 
to make you free. It's just not going to work.

	2) To make the GPL enforceable, you need to argue for a very loose 
definition of a derived work and you need to argue that a license can 
be enforceable even if it's not negotiated or explicitly agreed to 
prior to distribution. This will have the net effect of reducing 
everyone's freedom in very real ways.

	DS


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

             reply	other threads:[~2003-01-05  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05  5:10 Hell.Surfers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-04  5:05 Hell.Surfers
2003-01-04 15:42 ` Steven Barnhart
2003-01-04  3:15 Hell.Surfers

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=048250406050513DTVMAIL4@smtp.cwctv.net \
    --to=hell.surfers@cwctv.net \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rms@gnu.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®