Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264539AbUASLbN (ORCPT ); Mon, 19 Jan 2004 06:31:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264546AbUASLbN (ORCPT ); Mon, 19 Jan 2004 06:31:13 -0500 Received: from mail.webmaster.com ([216.152.64.131]:27066 "EHLO shell.webmaster.com") by vger.kernel.org with ESMTP id S264539AbUASLbL (ORCPT ); Mon, 19 Jan 2004 06:31:11 -0500 From: "David Schwartz" To: "Giuliano Pochini" Cc: Subject: RE: License question Date: Mon, 19 Jan 2004 03:31:02 -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) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2055 In-Reply-To: Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1640 Lines: 47 > On 17-Jan-2004 David Schwartz wrote: > >> > - Redistributions of source code must retain the above copyright > >> > notice, this list of conditions and the following disclaimers. > > Sorry, that's an "additional restriction" not permitted > > under the GPL. > These are in fact the points I wished your opinion about... > Actually these are requirements (like others said), not > use restrictions. There is no difference. Every requirement can be rephrased as an equivalent restriction. The requirement that you maintain the terms is the same as a restriction against removing them. > btw, IANAL and IP rights are a minefield. Definitely. > Since their code is C++ I already rewote everything in C, but it > also contains the binary firmwares which I can't rewrite. That's > why I asked you about the license. Then you have another problem. You can't place something under the GPL if you don't have the source code to it. How can you offer the source code to others if you don't have it? (Though my opinion seems to differ from the mainstream on this point. It is my opinion that you must possess the source code to any object code you wish to GPL.) > It's likely Echoaudio will change the license in the next release > to a dual GPL/custom license, so this will be no more an issue. Glad to hear that. > Thanks for you answers. Of course, you shouldn't rely upon them. DS - 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/