Changeset - 35f2952db5fd
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 8 years ago 2016-08-30 05:22:59
bkuhn@ebb.org
Add tech id in this tag.
1 file changed with 1 insertions and 1 deletions:
0 comments (0 inline, 0 general)
www/conservancy/static/copyleft-compliance/vmware-lawsuit-faq.html
Show inline comments
...
 
@@ -126,49 +126,49 @@
 
  the Linux kernel and his right to bring this action.  Second, VMware claims
 
  vmklinux is an “interoperability module” which communicates
 
  through a stable interface called VMK API.</dd>
 

	
 
  <dt>How did Christoph respond to VMware's statement of defense?</dt>
 

	
 
  <dd>Christoph's response discusses his extensive contributions to the Linux
 
  kernel and disputes the technical merits of VMware's assertions. The
 
  response points out that vmklinux is <strong>not</strong> an
 
  interoperability module, but rather an arbitrary separation of the Linux
 
  derived module from vmkernel.   Specifically, vmklinux is nonfunctional
 
  with any non-ESX OS, and vmklinux is tied intimately to a specific version
 
  of ESXi.  Vmklinux does not allow reuse of unmodified Linux drivers in
 
  binary or source form.  Christoph further points out that if the Court
 
  allows proprietarization of an arbitrary split portion of GPL'd computer
 
  programs, it could allow redistributors to trivially bypass the strong
 
  copyleft terms found in the GPL.  Finally, the response explains that
 
  vmkernel and vmklinux don't &ldquo;communicate over an interface&rdquo;,
 
  rather they run in the same process as a single computer program.  Thus,
 
  VMK API, as used by vmklinux, is not an &ldquo;interface&rdquo; as set
 
  forth in
 
  the <a href="http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009L0024&from=EN">EU
 
      Directive 2009/24/EC</a>.</dd>
 

	
 
  <dt>Can you explain further how VMware incorporated code from Linux into
 
  <dt id="tech">Can you explain further how VMware incorporated code from Linux into
 
  their kernel?</dt>
 

	
 
  <dd>
 
  <p id="diagram">
 
    Conservancy prepared this diagram to show the technical situation as we
 
    understand it.  The diagram compares the technical architecture of a full,
 
    running Linux kernel with a full, running VMware kernel:
 
    <p>
 
      <a href="/linux-compliance/linux-vs-vmkernel_en.png">
 
    <img class="inside-faq" alt="[Diagram of Linux and VMware running kernels]" src="/linux-compliance/linux-vs-vmkernel_en_scaled.png" /></a>
 
    </p>
 

	
 
    <p>If you want to download the diagram, it's available
 
    in <a href="/linux-compliance/linux-vs-vmkernel_en.svg">SVG
 
    (English)</a>, <a href="/linux-compliance/linux-vs-vmkernel_en.png">PNG
 
    (English)</a>, <a href="/linux-compliance/linux-vs-vmkernel_de.svg">SVG
 
    (German)</a>, and <a href="/linux-compliance/linux-vs-vmkernel_de.png">PNG
 
    (German)</a>.</p>
 
  </dd>
 

	
 
  <dt>Can you explain further in words (rather than a picture) about the central
 
  component in ESXi that the lawsuit alleges violates the GPL?</dt>
 
<dd>
 
    <p>The GPL violation at issue involves VMware's ESXi product.
0 comments (0 inline, 0 general)