2 ms·
As per the FAQ, this is much more than only drivers (http://sfconservancy.org/linux-compliance/linux-vs-vmkernel_en.png http://sfconservancy.org/linux-complianc
by belorn 12y ago
As per the FAQ, this is much more than only drivers (http://sfconservancy.org/linux-compliance/linux-vs-vmkernel_en.png http://sfconservancy.org/linux-compliance/linux-vs-vmkernel_...). It both about the internal code that makes up the vmklinux kernel, and drivers. The radix tree implementation for example is unlikely provided through a driver api.
The bigger question I think is how a non-technical judge will think when presented with a description of the vmkernel. Does it constitute one work, or is it a larger number of isolated small works that simply happens to work together in a independent fashion? Are the drivers in question separateable from the kernel and the finish "product" that wmware sells? Are wmware following what can be reasonable understood as the intended use of the licensed work?