mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: GPL issues
Date: Fri, 14 Apr 2006 11:56:55 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEHDLFAB.davids@webmaster.com> (raw)
In-Reply-To: <20060414175018.GD23222@vasa.acc.umu.se>


> Ahhh, but you're missing the whole point of the GPL.  The GPL is
> not really a normal license, it's a copyright license.  Basically,
> copyright law doesn't allow you to do *anything* with someone elses
> work without permission.  The GPL grants you such rights.
> However, in exchange for this, you agree to follow the license when
> redistributing your software that you built against the GPL:ed
> software.

	Bluntly, you're just completely wrong. If this were so, I could put up a
billboard with a poem and then sue everyone who read it.

	You should read http://www.copyright.gov/circs/circ1.html

	Notice, for example, that the rights granted under copyright do *not*
include the right to restrict the *use* of a work.

	Far from copyright law starting out with the premise that you can do
nothing with a work, it basically restricts copying or distribution of a
work and the production of works based on that work other than what's
necessary for ordinary use.

	Specifically, copyright does not protect ordinary use. If you buy a CD, you
get the right to use that CD simply by virtue of the fact that you lawfully
possess a lawfully made of the music on that CD.

	DS



  reply	other threads:[~2006-04-14 18:57 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11  6:31 Ramakanth Gunuganti
2006-04-11  8:42 ` Jesper Juhl
2006-04-11 10:51   ` Martin Mares
2006-04-11 17:46   ` Horst von Brand
2006-04-11 13:49 ` Kyle Moffett
2006-04-11 15:49   ` Ramakanth Gunuganti
2006-04-11 16:07     ` linux-os (Dick Johnson)
2006-04-11 16:29       ` Stefan Smietanowski
2006-04-11 16:13     ` Adrian Bunk
2006-04-11 16:15     ` Kyle Moffett
2006-04-11 16:23     ` Dave Neuer
2006-04-11 18:58     ` Jan Engelhardt
2006-04-14 11:39       ` David Schwartz
2006-04-14 14:54         ` linux-os (Dick Johnson)
2006-04-14 17:50         ` David Weinehall
2006-04-14 18:56           ` David Schwartz [this message]
2006-04-15 11:55             ` Alan Cox
2006-04-15 13:04               ` Steven Rostedt
2006-04-15 18:49               ` David Schwartz
2006-04-11 15:49   ` Ramakanth Gunuganti
2006-04-11 23:06 ` David Weinehall
2006-04-12  2:38   ` Joshua Hudson
2006-04-12  3:18     ` Mark Lord
2006-04-12  5:00       ` Kyle Moffett
2006-04-12  5:31       ` Arjan van de Ven
2006-04-12  5:45         ` jdow
2006-04-12  6:01           ` David Weinehall
2006-04-12  6:26             ` jdow
2006-04-12  9:13             ` Stefan Smietanowski
2006-04-12 11:33               ` Olivier Galibert
2006-04-12 14:51           ` Arjan van de Ven
2006-04-13 22:07             ` Mark Lord
2006-04-15 11:14               ` Arjan van de Ven
2006-04-13 22:17         ` Mark Lord
2006-04-15 11:15           ` Arjan van de Ven
2006-04-11 23:12 ` Alan Cox
2006-04-12  7:01 Pramod Srinivasan
2006-04-12  8:16 ` David Weinehall
2006-04-12  9:06 ` Jan Engelhardt
2006-04-12  9:22   ` Stefan Smietanowski
2006-04-12  9:40     ` Martin Mares
2006-04-12  9:28   ` Alan Cox
2006-04-14 11:39 ` David Schwartz

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=MDEHLPKNGKAHNMBLJOLKAEHDLFAB.davids@webmaster.com \
    --to=davids@webmaster.com \
    --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®