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.
This commit is contained in:
parent
b59142e32c
commit
fed9826bc0
1 changed files with 9 additions and 0 deletions
|
@ -180,6 +180,15 @@ Code, and for which (at least some) source code is provided.
|
||||||
whole was developed by modifying Linux code in tandem with
|
whole was developed by modifying Linux code in tandem with
|
||||||
modifications to “vmkernel” in a tightly coupled manner.</p>
|
modifications to “vmkernel” in a tightly coupled manner.</p>
|
||||||
</dd>
|
</dd>
|
||||||
|
|
||||||
|
<dt id="shim-meaningless">Wait, is Conservancy proposing that a
|
||||||
|
“shim” 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
|
<dt>Can you give a <em>specific</em> example, with code, showing how
|
||||||
VMware combined Linux source code with their binary-only components?</dt>
|
VMware combined Linux source code with their binary-only components?</dt>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue