diff --git a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html index 1ad10ccd..c70e7874 100644 --- a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html +++ b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html @@ -162,6 +162,7 @@ Code, and for which (at least some) source code for which is provided. obligations and allow them to keep certain code in their kernel proprietary? +
Many in the media have talked about the possibility that VMware might use some so-called “shim layer” between Linux code and VMware's proprietary code. While, for decades, there has been much talk of @@ -177,7 +178,7 @@ Code, and for which (at least some) source code for which is provided. 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 “vmkernel” in a tightly coupled manner.
- +bin/vmtar
inside
Software Foundation