From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
xen-devel@lists.xensource.com, Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, Linus Torvalds <torvalds@osdl.org>,
James.Bottomley@steeleye.com, pazke@donpac.ru
Subject: Re: A proposal - binary
Date: Fri, 04 Aug 2006 22:26:40 +0100 [thread overview]
Message-ID: <1154726800.23655.273.camel@localhost.localdomain> (raw)
In-Reply-To: <44D3B0F0.2010409@vmware.com>
Ar Gwe, 2006-08-04 am 13:41 -0700, ysgrifennodd Zachary Amsden:
> committed to working on it. Which is why I wanted feedback on what we
> have to do to make sure our ESX implementation is done in a way that is
> acceptable to the community. I too would like to push for an interface
> in 2.6.19, and we can't have confusion on this issue be a last minute
> stopper.
In part thats a legal question so only a lawyer can really tell you what
is and isn't the line for derivative works.
Philosophically I can see the argument that the moment you hit a
hypervisor trap its akin to running another app (and an app which
communicates via that interface with many othr apps) so your Linux
kernel side code would be GPL and whatever it fires up which handles the
trap come syscall probably isn't. But I'm not a lawyer and neither you
nor anyone else, nor a court reviewing a case should consider the
statement above a guideline of intent.
Alan
next parent reply other threads:[~2006-08-04 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D1CC7D.4010600@vmware.com>
[not found] ` <20060803190605.GB14237@kroah.com>
[not found] ` <44D24DD8.1080006@vmware.com>
[not found] ` <20060803200136.GB28537@kroah.com>
[not found] ` <20060804183448.GE11244@sequoia.sous-sol.org>
[not found] ` <44D3B0F0.2010409@vmware.com>
2006-08-04 21:26 ` Alan Cox [this message]
2006-08-05 1:14 ` A proposal - binary James Bottomley
2006-08-05 5:37 ` Zachary Amsden
2006-08-05 10:42 ` Adrian Bunk
2006-08-05 11:50 ` Alan Cox
2006-08-04 22:01 ` Andi Kleen
2006-08-04 22:39 ` Zachary Amsden
2006-08-04 22:52 ` Andi Kleen
2006-08-04 22:43 ` David Lang
2006-08-05 10:47 ` Adrian Bunk
2006-08-05 11:57 ` Andi Kleen
2006-08-05 1:30 ` James Bottomley
2006-08-05 4:33 ` Zachary Amsden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154726800.23655.273.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@donpac.ru \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).