linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: jmerkey@galt.devicelogics.com
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	"Jeff V. Merkey" <jmerkey@drdos.com>,
	"jmerkey@comcast.net" <jmerkey@comcast.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Possible GPL Violation of Linux in Amstrad's E3 Videophone
Date: Sat, 02 Oct 2004 11:27:25 +0100	[thread overview]
Message-ID: <415E828D.5020705@jonmasters.org> (raw)
In-Reply-To: <20041002064620.GA8568@galt.devicelogics.com>

jmerkey@galt.devicelogics.com wrote:

[ You snipped the original sender identification - the quote below forms 
part of a response from Theodore Ts'o. ]

>>You should have attended Harald Welte's "Enforcing the GPL" talk at
>>the Linux Kongress this year.  There are plenty of worked examples
>>where Harald and the Netfilter kernel developers have successfully
>>taken commercial vendors to court and got them to either (a) release
>>their enhancements under the GPL, or (b) stop distributing the GPL'ed
>>code.  It can and has been done in the real world, with multiple
>>vendors, and they haven't lost a case yet.
>>
>>					- Ted

> If you can obtain discovery and catch people with a "smoking gun."
> Very hard to do.

The smoking gun is very often obtained by dissassembling the device 
firmware or program binaries and/or runing string comparisons.

> Inside some of these big companies with lots
> of money, most folks won't come clean or spoilate evidence.

It's hard to spoil the evidence when all of your customers have it.

<snip more anti-Novell comments>

> The simplest way is to add a clause to the GPL requiring people
> to obtain a license from the copyright holders if code is 
> ever used in a commerical venture.  There's no wiggle room --
> they will have to sign and ackowledge they accepted the GPL
> and ackowledge their obligations from the copyright holder.   

I don't know what the world is like where you are (I admit that if 
you're in the States you probably *are* more repressed than I am in the 
UK right now) but you seem to have some extreme paranoia which seems 
more than a little unfounded. The above is completely unnecessary - it 
does nothing that using the GPL already does not do - but you seem to 
have convinced yourself that the real problem here is the GPL.

Jon.


  parent reply	other threads:[~2004-10-02 10:28 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
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 [this message]
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=415E828D.5020705@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=jmerkey@galt.devicelogics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).