This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] RE: Does it legal to analysize XEN source code and write

To: Tao Shen <taoshen1983@xxxxxxxxx>
Subject: Re: [Xen-users] RE: Does it legal to analysize XEN source code and write a book about it
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Mon, 17 Sep 2007 12:50:12 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Simon Crosby <simon@xxxxxxxxxxxxx>
Delivery-date: Mon, 17 Sep 2007 04:44:57 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=7UeBY+F+luUpuagVRk2ScSLXuSmG7JNiaPUuTQyYqdo=; b=cFCnQhqNtdbalv6oqrm+4a/xwLlQPG4QwLsDsd2BazzYqiPBTToDYn/BBExmMtaPh8gboKgx/rXwlwJwRfr7CQHYIX1TEMEJmaoz9370gXpdDl9EXM5zazIpz0sm5BPWOco5qBJW2cTVglqxVlQ8qjY7uS2IImVCjRNKlh1bb1M=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=tijUQ+2nVJhme9FpEdgkJto0EPgcm6hEXUuGc4HGhDC47HLs0khRf/GOdyKZ4+tK9L5jGFXt31PFF0ve7o0lSeT3FJByODiNSBYDWDVC4wx4bPFbE0tHQSQBjQQiZIWJlq3HPmOLAyZX1ChQaO/Spq5ZyGYorks96A1qQb8HS+w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46EE60DD.5030008@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <E1IW3Nf-0005uV-R6@host-192-168-0-1-bcn-london> <0326530267625D42A4E36594FDD0D143021FF153@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <46EE53F2.2020206@xxxxxxxxx> <46EE60DD.5030008@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070809)
Tao Shen wrote:

7. Some of the examples in the open source industry right now include: using PostgreSQL based code which is GPL'd, add a non-GPL'd replication suite to it, and call it enterpriseDB. Using PostgreSQL based code, tweak some variables, add some non-GPL'd code (interfaced to the GPL'd one) to do distributed join and call it "bizgres" and "greenplum". MySQL's Enterprise vs Community editions....the examples are all other the place. All of them push the GPL boundary but don't violate it. And what I call the "wrapper GPL" type products, and "dual licensing". No, it's all perfect legal. From an ethics perspective...it's arguable.

Feel free to discuss this as you see fit.

Entire OS's are built this way, such as RHEL with its additional Clustering tools and its RedHat Network management tools. Zmanda does it with the Amanda sotware as well, and there are numerous commercial Nagios and MRTG management toolsets that are not themselves freeware or open source. Tivo does their own special trick of locking down the software so it can't be patched or modified, even though they publish source to GPL tools they change, and that led partly to the changes in GPLv3.

So it's an accepted practice, as long as you don't go over the carefully drawn copyright lines and pull the Netgear trick of "we'll use glibc, modify it, and just not tell anyone."

Xen-users mailing list