[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Copyright/licensing info ?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: B Thomas <bjthomas3@xxxxxxxxx>
  • Date: Wed, 14 Dec 2005 10:13:06 -0500
  • Delivery-date: Wed, 14 Dec 2005 15:15:02 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=UXG2zgZY9IULl3i7lad2oBR9vTfxVlfcZeYsCQq1VqQYNCoiNCX1YVs6FLfQ8T0x4XmcbZYa58P/zxI19TWY/8p25IK2iOJnPsUjAR67OvXaHN1r64JOXPwpuJ0QnHb2St6Wc9fmnjSZIdVJAeesZfIxwRfLY+5qRG5rBuMoyW0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I noticed this change and it made me wonder...

So, what will the final license/copyright be ? There's precious little text here now.

Is there, or will there, be some cohesive mapping of licensing boundaries ? That is,
POSIX provides a clean API and licensing boundary for user programs. The hypervisor
states (somewhere, I think) ahout it's boundary with callers. Are these changes
to copyright/license following a plan ? I assume that they are, and would like
to understand the overall plan for which systems/subsystems/components are
to be under what license.

Thanks,
-b



--- a/xen/include/public/io/xenbus.h Sat Dec 10 14:57:11 2005
+++ b/xen/include/public/io/xenbus.h Sat Dec 10 15:07:03 2005
@@ -4,28 +4,6 @@
* Xenbus protocol details.
*
* Copyright (C) 2005 XenSource Ltd.
- *
- * This file may be distributed separately from the Linux kernel, or
- * incorporated into other software packages, subject to the following
- * license:
- *
- * Permission is hereby granted, free of charge, to any person obtaining a
- * copy of this source file (the "Software"), to deal in the Software without
- * restriction, including without limitation the rights to use, copy, modify,
- * merge, publish, distribute, sublicense, and/or sell copies of the Software,
- * and to permit persons to whom the Software is furnished to do so, subject
- * to the following conditions:
- *
- * The above copyright notice and this permission notice shall be included in
- * all copies or substantial portions of the Software.
- *
- * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
- * DEALINGS IN THE SOFTWARE.
*/

#ifndef _XEN_XENBUS_H
--- a/xen/include/public/io/xs_wire.h	Sat Dec 10 14:57:11 2005
+++ b/xen/include/public/io/xs_wire.h Sat Dec 10 15:07:03 2005
@@ -2,27 +2,6 @@
* Details of the "wire" protocol between Xen Store Daemon and client
* library or guest kernel.
* Copyright (C) 2005 Rusty Russell IBM Corporation
- *
- * This file may be distributed separately from the Linux kernel, or
- * incorporated into other software packages, subject to the following license:
- *
- * Permission is hereby granted, free of charge, to any person obtaining a copy
- * of this source file (the "Software"), to deal in the Software without
- * restriction, including without limitation the rights to use, copy, modify,
- * merge, publish, distribute, sublicense, and/or sell copies of the Software,
- * and to permit persons to whom the Software is furnished to do so, subject to
- * the following conditions:
- *
- * The above copyright notice and this permission notice shall be included in
- * all copies or substantial portions of the Software.
- *
- * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
- * IN THE SOFTWARE.
*/

#ifndef _XS_WIRE_H
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.