Report from the VMware GPL court hearing
laforge.gnumonks.org
Report from the VMware GPL court hearing
1–10 of 50 posts
Re: Report from the VMware GPL court hearing
#2Re: Report from the VMware GPL court hearing
#3I would be interested to know if there are any other court cases that have had similar outcomes in other countries? Or is this really a first for GPL
Re: Report from the VMware GPL court hearing
#4I would be interested to know if there are any other court cases that have had similar outcomes in other countries? Or is this really a first for GPL
Re: Report from the VMware GPL court hearing
#5[...] the VMware defense in claiming that overall, they could only find very few functions that could be attributed to Christoph, and that this may altogether be only 1% of the Linux code they use in VMware ESXi.
At times their lawyers made statements like linux is this small yellow box in the left bottom corner (of our diagram). So of course already the diagrams are drawn in a way to twist the facts according to their view on reality.
Re: Report from the VMware GPL court hearing
#6Some quotes that I feel shows VMware's attitude towards the software freedom community: [...] the VMware defense in claiming that overall, they could only find very few functions that could be attributed to Christoph, and that this may altogether be only 1% of the Linux code they use in VMware ESXi. At times their lawyers made statements like linux is this small yellow box in the left bottom corner (of our diagram).…
Re: Report from the VMware GPL court hearing
#7Re: Report from the VMware GPL court hearing
#8Some quotes that I feel shows VMware's attitude towards the software freedom community: [...] the VMware defense in claiming that overall, they could only find very few functions that could be attributed to Christoph, and that this may altogether be only 1% of the Linux code they use in VMware ESXi. At times their lawyers made statements like linux is this small yellow box in the left bottom corner (of our diagram).…
Re: Report from the VMware GPL court hearing
#9Some quotes that I feel shows VMware's attitude towards the software freedom community: [...] the VMware defense in claiming that overall, they could only find very few functions that could be attributed to Christoph, and that this may altogether be only 1% of the Linux code they use in VMware ESXi. At times their lawyers made statements like linux is this small yellow box in the left bottom corner (of our diagram).…
Considering that there are definitely more than a hundred major contributors to the Linux kernel, it's not unreasonable that a single one's contributions only make up 1% of the total.
Re: Report from the VMware GPL court hearing
#10Some quotes that I feel shows VMware's attitude towards the software freedom community: [...] the VMware defense in claiming that overall, they could only find very few functions that could be attributed to Christoph, and that this may altogether be only 1% of the Linux code they use in VMware ESXi. At times their lawyers made statements like linux is this small yellow box in the left bottom corner (of our diagram).…
Here's how I see it. Vmkernel has a driver API. It's documented, versioned, comes with a ddk and has drivers written directly to it.
As we all know, Linux basically has driver apis. They are not as explicit as the vmkernel driver apis; they are not versioned and deliberately unstable - but if you've written a line of kernel code you know they are there.
Now it seems it is OK to ship a binary blob driver that links against Linux driver apis. Nvidia, ati, lots of arm type boards and now zfs. I say seems because, well, so far everyone has pretty much gone along with it. In some of the comments on zfs, I see people go as far to say that the Linux driver APIs are tacitly considered lgpl (ie. similar to why you can ship a binary against glibc - although obviously glibc has made the exception explicit)
Can I do the reverse? Implement a GPL licensed wrapper that converts the Linux driver API to one provided by a binary blob (ie. what vmklinux does talking to vmkernel) and thus use the drivers?
I don't know, I think it's a good question to find an answer to.