From owner-freebsd-hackers Mon Jun 19 02:11:14 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA04942 for hackers-outgoing; Mon, 19 Jun 1995 02:11:14 -0700 Received: from iiit.swan.ac.uk (root@iifeak.swan.ac.uk [137.44.100.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA04930 for ; Mon, 19 Jun 1995 02:10:43 -0700 Message-Id: From: iialan@iifeak.swan.ac.uk (Alan Cox) Subject: Re: GPL code in freebsd? To: freebsd-hackers@freebsd.org Date: Mon, 19 Jun 1995 09:58:43 +0100 (BST) In-Reply-To: <199506162152.XAA05538@uriah.heep.sax.de> from "J Wunsch" at Jun 16, 95 11:52:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1210 Sender: hackers-owner@freebsd.org Precedence: bulk > Due to the currently very limited scope of the isdn driver (only > german switch protocols, only a very limited range of hardware > supported), this is unlikely to happen. (And then: it's the problem > of those who're going to distribute those binary versions.) > > It's not our problem if the defenders of the GPL are unable to read > their own license. :-) I can read licenses thank you. The US/UK definitions of 'seperate works' is such that a BSD kernel linked with the GPL'd driver and distributed must be done so under the GPL. As a pile of source trees the case is less clear. --- These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.