linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@drdos.com>
To: Valdis.Kletnieks@vt.edu
Cc: jmerkey@comcast.net, linux-kernel@vger.kernel.org
Subject: Re: Possible GPL Violation of Linux in Amstrad's E3 Videophone
Date: Fri, 01 Oct 2004 13:46:47 -0600	[thread overview]
Message-ID: <415DB427.7050108@drdos.com> (raw)
In-Reply-To: <200410011934.i91JYU2t014578@turing-police.cc.vt.edu>


>Umm.. It's OK to take the GPL'ed source and make your own fork for your own
>amusement.  Trying to distribute it without accepting the GPL on the parts
>you're shipping copies of *is* a problem. As the COPYING file says:
>
>  5. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Program or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Program (or any work based on the
>Program), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Program or works based on it.
>
>So you have three choices: You can accept the terms of the GPL, and comply
>with them, or you can not ship those pieces covered by the GPL (basically
>the entire kernel), or you can ship it in violation and wait for the hate
>mail to start arriving..... 
> 
>
>  
>
And the hate mail is the only thing that will arrive.   The GPL doesn't 
really seem
to protect anyone since the copyright holders really can't do much with 
it.  I've
got a bunch of people using GPL code I've put out there in all sorts of 
commercial
products and Can't do anything to them for failing to return changes.  
They can always
say they didn't accept the license then convert the code into their own IP .

Jeff

  reply	other threads:[~2004-10-01 20:27 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 17:40 Possible GPL Violation of Linux in Amstrad's E3 Videophone jmerkey
2004-10-01 18:23 ` Jesse Pollard
2004-10-01 19:34 ` Valdis.Kletnieks
2004-10-01 19:46   ` Jeff V. Merkey [this message]
2004-10-01 20:38     ` Geert Uytterhoeven
2004-10-01 20:40     ` Valdis.Kletnieks
2004-10-01 22:09 ` Jon Masters
2004-10-01 21:53   ` Jeff V. Merkey
2004-10-01 23:51     ` Michael Poole
2004-10-02  2:00     ` Theodore Ts'o
     [not found]       ` <20041002064620.GA8568@galt.devicelogics.com>
2004-10-02 10:27         ` Jon Masters
2004-10-02 17:34     ` Alan Cox
2004-10-03 11:46       ` Willy Tarreau
2004-10-03 11:59         ` Jon Masters
2004-10-03 22:01         ` Alan Cox
2004-10-04  0:23           ` Kyle Moffett
2004-10-07 19:21       ` Jeff V. Merkey
2004-10-07 20:24         ` Chris Friesen
2004-10-07 21:22           ` Jeff V. Merkey
2004-10-07 22:32             ` Chris Friesen
2004-10-07 22:57             ` Hua Zhong
2004-10-08  8:19             ` Henning P. Schmiedehausen
2004-10-07 21:07         ` Rik van Riel
2004-10-07 21:16           ` Jeff V. Merkey
2004-10-07 21:40         ` Kyle Moffett
2004-10-07 21:17           ` Jeff V. Merkey
2004-10-07 22:02             ` Kyle Moffett
2004-10-07 21:29               ` Jeff V. Merkey
2004-10-08 12:27                 ` Ingo Molnar
2004-10-08 18:24                   ` Geert Uytterhoeven
2004-10-08 18:42                     ` Ingo Molnar
2004-10-09  9:50                       ` James Courtier-Dutton
2004-10-08 12:16               ` Alan Cox
2004-10-07 22:18             ` Dave Jones
2004-10-07 21:51               ` Jeff V. Merkey
2004-10-07 22:41                 ` Dave Jones
2004-10-08  0:47                   ` Jeff Garzik
2004-10-07 23:50                 ` viro
2004-10-08  0:40                 ` Jesper Juhl
2004-10-08  0:59                   ` Jon Masters
     [not found]                     ` <20041008032034.GD3528@galt.devicelogics.com>
2004-10-08  7:15                       ` Jon Masters
2004-10-08 12:38                         ` Gene Heskett
2004-10-08 12:50                           ` Gene Heskett
2004-10-08 13:48                           ` Bruce Ferrell
2004-10-08 15:14                             ` Gene Heskett
2004-10-08  2:48                 ` Erik Andersen
2004-10-10  6:35               ` Brian Litzinger
2004-10-10 13:25                 ` Alan Cox
2004-10-10 22:26                   ` Jon Masters
2004-10-11 11:57                     ` Tonnerre
2004-10-08  2:40         ` Erik Andersen
2004-10-08  8:50           ` Bernd Petrovitsch
2004-10-08 11:08             ` William Lee Irwin III
2004-10-04 20:26     ` Jesse Pollard
2004-10-02 12:35 ` James Courtier-Dutton
2004-10-04 18:03 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2004-09-29 13:44 Ralph Corderoy
2004-10-01 14:52 ` Denis Vlasenko
2004-10-01 14:20   ` Alan Cox
2004-10-01 15:59     ` Ralph Corderoy
2004-10-01 16:00       ` Alan Cox
2004-10-01 16:24       ` Jon Masters
2004-10-01 15:59         ` Alan Cox
2004-10-01 17:18           ` Jon Masters
2005-01-07 21:48           ` Jonathan McDowell
2005-01-15 13:43             ` Jonathan McDowell
2005-01-26 16:47               ` Jonathan McDowell
2004-10-01 17:24       ` Tigran Aivazian
2004-10-01 16:14     ` James Courtier-Dutton

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=415DB427.7050108@drdos.com \
    --to=jmerkey@drdos.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jmerkey@comcast.net \
    --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;
as well as URLs for NNTP newsgroup(s).