Changeset - fed9826bc02f
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 9 years ago 2015-03-17 02:05:50
bkuhn@ebb.org
Add note to reiterate shim layer answer.

It appears that some in the media believe the understand above says the
opposite, so I've corrected it.
1 file changed with 9 insertions and 0 deletions:
0 comments (0 inline, 0 general)
www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
Show inline comments
...
 
@@ -177,12 +177,21 @@ Code, and for which (at least some) source code is provided.
 
    “shim layers”.  Conservancy's analysis of VMware's ESXi
 
    product, in fact, indicates that VMware rather flagrantly combined Linux
 
    code in their own kernel, and evidence seems to indicate the work as a
 
    whole was developed by modifying Linux code in tandem with
 
    modifications to &ldquo;vmkernel&rdquo; in a tightly coupled manner.</p>
 
    </dd>
 

	
 
   <dt id="shim-meaningless">Wait, is Conservancy proposing that a
 
      &ldquo;shim&rdquo; layer is a viable solution for VMware to comply with
 
      GPL?</dt>
 

	
 
    <dd>No, in fact, as we say above, Conservancy doesn't think the
 
        phrase 'shim layer' has any meaning, despite its regular use in the
 
        media.</dd>
 

	
 
    <dt>Can you give a <em>specific</em> example, with code, showing how
 
    VMware combined Linux source code with their binary-only components?</dt>
 

	
 
     <dd><p>There are numerous examples available that show this.  The
 
       details of alleged infringement specifically relating to Hellwig's
 
       contributions to Linux are of course the main matter of the
0 comments (0 inline, 0 general)