Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 31 Oct 2001 15:00:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 31 Oct 2001 15:00:20 -0500 Received: from boreas.isi.edu ([128.9.160.161]:26583 "EHLO boreas.isi.edu") by vger.kernel.org with ESMTP id ; Wed, 31 Oct 2001 15:00:06 -0500 To: Larry McVoy cc: Rik van Riel , Timur Tabi , Alan Cox , linux-kernel@vger.kernel.org Subject: [OT] Module Licensing? In-Reply-To: Your message of "Wed, 31 Oct 2001 09:22:28 PST." <20011031092228.J1506@work.bitmover.com> Date: Wed, 31 Oct 2001 11:55:01 -0800 Message-ID: <4986.1004558101@ISI.EDU> From: Craig Milo Rogers Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >> 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. > >This is obviously incorrect, that would say that > > #include > >means my app is now GPLed. Good luck enforcing that. Your compiled object module might be a derived work, hence its distribution would be restricted by the terms of the GPL version 2. Your source code file would not be a derived work (under certain currently widely-held assumptions about interface copyrights), and hence could be distributed without restriction by the GPL. Usual disclaimer: I am not a lawyer. Craig Milo Rogers - 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/