Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 31 Oct 2001 12:37:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 31 Oct 2001 12:37:23 -0500 Received: from garrincha.netbank.com.br ([200.203.199.88]:4616 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Wed, 31 Oct 2001 12:37:18 -0500 Date: Wed, 31 Oct 2001 15:37:45 -0200 (BRST) From: Rik van Riel X-X-Sender: To: Timur Tabi Cc: Subject: Re: Module Licensing? In-Reply-To: <3BE034F6.8070201@interactivesi.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 31 Oct 2001, Timur Tabi wrote: > Rik van Riel wrote: > > > Since your program, which happens to consist of one open > > source part and one proprietary part, is partly a derived > > work from the kernel source (by using kernel header files > > and the inline functions in it) your whole work must be > > distributed under the GPL. > > I contest your meaning of the word "work". The open source portion of > my module is one "work", and the closed source portion is another > "work". I could deliver these two works as separate tarballs, if I > wanted. Let me quote you, from 2 emails back in the thread: "The fact that the open source portions and the closed source portions can't function on their own is irrelevant, IMHO." The irrelevance here is IYHO ... it may well be judged that since these two portions of the work need each other in order to function, the thing really is one work. You're well into the danger zone here... regards, Rik -- DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/ http://www.surriel.com/ http://distro.conectiva.com/ - 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/