From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263810AbTLEGew (ORCPT ); Fri, 5 Dec 2003 01:34:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263823AbTLEGew (ORCPT ); Fri, 5 Dec 2003 01:34:52 -0500 Received: from mail.webmaster.com ([216.152.64.131]:50334 "EHLO shell.webmaster.com") by vger.kernel.org with ESMTP id S263810AbTLEGeu (ORCPT ); Fri, 5 Dec 2003 01:34:50 -0500 From: "David Schwartz" To: Cc: "Paul Adams" , Subject: RE: Linux GPL and binary module exception clause? Date: Thu, 4 Dec 2003 22:34:36 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20031205045803.GA12038@codepoet.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Or maybe you feel like making a Harry Potter knockoff. Go ahead > and write whatever you want in the privacy of your own home. If > you dare to try distributing such a knock off novel, you will shortly > find Time-Warner sending a herd of lawyers your direction [2]. Yes, but they will cite the prohibition against *creating* derived works. > Similarly, nobody cares what kernel modules you feel like making > and loading in the privacy of your own home. There's a difference between what you can and can't do and what you can and can't get away with. You can get away with making a Harry Potter sequel in the privacy of your own home because nobody would find about it, however legally, you do not have the right to create the derived work. However, if you did have the right to create the derived work, you'd automatically have the right to distribute it to anyone who already owned the original work from which it was derived. > > So long as it must be mixed with the original work (and isn't > > already), it's not clear that it's a derived work as it sits. > > Again, otherwise any program that used 'malloc' would be a > > derived work of any implementation of 'malloc'. > The act of compiling a program and linking that program with a > library certainly does create a derivitive work of that library. Right, however, you have the right to create that derivative work. > Try linking your program with the 30-day evaluation version of > Intel's Math Kernel Library and distributing the result without > paying them for a license. Try using Qt in a non-GPL closed > source product without paying Trolltech. Try using MS Visual > Studio to create and distribute your own competing compiler. > Guess how fast you would have herds of lawyers visiting to > discuss your opinions of what is and is not a derived work? These cases are much more interesting, except for the MS VC case. In the MS VC case, there's a EULA that courts are likely to consider part of the sales contract. As for the others, I think you'd have a very good chance of winning them. See, for example, ProCD v. Zeidelberg (sp?). In the absence of a shrink wrap or clickthrough at least, it would seem you only have those specific rights copyright grants you, and the right to restrict the distribution of derived works is not one of those rights. DS