website Changeset - b59142e32c80 · Conservancy Kallithea

Changeset - b59142e32c80

Parent rev.

Child rev.

[Not reviewed]

Merge

0 2 0

Bradley Kuhn (bkuhn) - 9 years ago 2015-03-12 17:09:27
bkuhn@ebb.org

Merge branch 'master' from upstream changes.

1 file changed with 17 insertions and 16 deletions:

www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html

0 comments (0 inline, 0 general)

www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html

➞

Show inline comments

@@ ... / @@ -141,3 +141,3 @@ @@
     Conservancy independently reviewed ESXi 5.5 and its incomplete
-      <acronym title="complete, corresponding source">CCS</acronym>
+      <abbr title="complete, corresponding source">CCS</abbr>
     release as part of our GPL enforcement efforts described above.</p>
@@ ... / @@ -150,3 +150,3 @@ @@
             <li>the kernel module &ldquo;vmklinux&rdquo;, which contains modified Linux
-Code, and for which (at least some) source code for which is provided.
 Code, and for which (at least some) source code is provided.
             <li>other kernel modules with device drivers, most of which are
@@ ... @@
     <p>Conservancy examined the incomplete CCS alongside the
-           binary &ldquo;vmkernel&rdquo; component.  Such examination indicates that function
+           binary &ldquo;vmkernel&rdquo; component.  Such examination indicates that functions
            in &ldquo;vmkernel&rdquo; do make function calls to Linux's kernel code
@@ ... @@
            ESXi 5.5.0 Update 2 (5.5U2).  A small excerpt from that file, found in the
            function <code>LinuxPCIDeviceRemoved()</code>, reads as follows:
            function <code>LinuxPCIDeviceRemoved()</code>, reads as follows:</p>
 <pre>
@@ ... / @@ -224,3 +225,3 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
 </pre>
-</p>
 <p>The function, <code>vmk_PCIGetDeviceName()</code> must be defined, with an
@@ ... / @@ -236,3 +237,4 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
   <code>vmklinux_9</code> module.  Note the following output in the &ldquo;SYMBOL
   TABLE&rdquo; section:
   TABLE&rdquo; section:</p>
 <pre>
@@ ... / @@ -241,4 +243,6 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
 <p>
 &hellip;and the following lines found in the  &ldquo;RELOCATION RECORDS FOR
 [.text]&rdquo; section:
 </p>
@@ ... / @@ -250,3 +254,2 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
 </pre>
 </p>
@@ ... / @@ -266,3 +269,4 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
   &ldquo;vmkernel&rdquo; component.  An <code>objdump -x</code> yields this
   &ldquo;SYMBOL TABLE&rdquo; section:
   &ldquo;SYMBOL TABLE&rdquo; section:</p>
 <pre>
@@ ... / @@ -271,3 +275,3 @@ VMKAPI_MODULE_CALL_VOID(pciDevExt->moduleID, @@
 &hellip; which indicated these binary file contains the function body
+<p>&hellip; which indicated these binary file contains the function body
 for  <code>vmk_PCIGetDeviceName</code>.</p>
@@ ... / @@ -282,3 +286,3 @@ for <code>vmk_PCIGetDeviceName</code>.</p> @@
 <p>Given this evidence and related contextual clues, the only logical
   conclusions are:
+  conclusions are:</p>
     <ul><li><code>vmklinux_9</code>, as a binary object, dynamically links
@@ ... / @@ -302,3 +306,2 @@ for <code>vmk_PCIGetDeviceName</code>.</p> @@
     </ul>
     </p>
 <p>The above is but one piece of evidence among many, but hopefully it helps
@@ ... / @@ -315,3 +318,3 @@ previously-mentioned <code>linux_pci.c</code>, @@
   <p>To obtain the source components, follow these steps (no login is required):
+  <p>To obtain the source components, follow these steps (no login is required):</p>
@@ ... / @@ -346,5 +349,4 @@ previously-mentioned <code>linux_pci.c</code>, @@
 </ol>
 </p>
   <p>To obtain the binary components, follow these steps (a login is required):
+  <p>To obtain the binary components, follow these steps (a login is required):<p>
@@ ... / @@ -397,5 +399,4 @@ at <code>bin/vmtar</code> inside @@
 </ol>
 </p>
-  <p>Note that VMware may present you with <acronym title="End User Licensing Agreement">EULA</acronym>s and <acronym title="Terms of Service">ToS</acronym> when you download
+  <p>Note that VMware may present you with <abbr title="End User Licensing Agreement">EULA</abbr>s and <abbr title="Terms of Service">ToS</abbr> when you download
   software from VMware's website.  Conservancy strongly suggests that you review these

0 comments (0 inline, 0 general)