VMWare Taken to Court Over GPL Violation
31–40 of 299 posts
Re: VMWare Taken to Court Over GPL Violation
#32As a VMWare customer, this makes me consider their ethics. If they're unethical, shouldn't we look into switching away from their product? I'm not aware of many competitors in their market space - Hyper-V certainly, but that's less of an option for some. Short of rearchitecting our service as a series of containers, what action can conscientious corporate leaders take?
Oracle's Virtualbox? Oh, you said ethics...nevermind.
But then, you could use Xen directly.
Re: VMWare Taken to Court Over GPL Violation
#33Edit: "[The USD] is our currency, but it's your problem.", John Bowden Connally, Jr.
Obviously here are people who like it that way.
Re: VMWare Taken to Court Over GPL Violation
#34Earlier quoted context omitted.
I'm not fully up-to-date on this case, but there is a bit of wiggle room on what counts as a derivative work, even in kernelspace. My favorite example is OpenAFS. Development of the AFS kernel module started in 1983, so the code is a decade older than Linux itself. So it's hard to argue that openafs.ko is a derivative work of Linux, and since it continues to run on several kernels other than Linux (Darwin, Solaris, N…
The issue is that there's linking, not merely calling from. As for "what came first"- the license (which is a legal contract) specifies what is and isn't allowed. The LGPL would work in the way you are saying that VMWare might like it to work- where linking isn't the same as deriving. The fact that these two licenses exist demonstrates that distinction clearly. The issue will be whether or not a judge understands the…
Re: VMWare Taken to Court Over GPL Violation
#35Any litigation of the GPL is more than likely more dangerous for the GPL than it is for the companies. A relaxing of the understood requirements of using and distributing GPL code could cause an avalanche of fall out from formerly protected code becoming less protected. If I was this organization I would only risk a lawsuit of something that would have profound positive consequences for open source. VMware's risk is…
[1] http://www.ifross.org/sites/default/files/130618%20Urteil%20... [2] http://www.it-recht-kanzlei.de/Urteil/2767/LG_Frankfurt_6.Zi... [3] http://www.internetrecht-rostock.de/urheberrecht23-gpl-lg-mu...
Re: VMWare Taken to Court Over GPL Violation
#36Any litigation of the GPL is more than likely more dangerous for the GPL than it is for the companies. A relaxing of the understood requirements of using and distributing GPL code could cause an avalanche of fall out from formerly protected code becoming less protected. If I was this organization I would only risk a lawsuit of something that would have profound positive consequences for open source. VMware's risk is…
Re: VMWare Taken to Court Over GPL Violation
#37Re: VMWare Taken to Court Over GPL Violation
#38As a VMWare customer, this makes me consider their ethics. If they're unethical, shouldn't we look into switching away from their product? I'm not aware of many competitors in their market space - Hyper-V certainly, but that's less of an option for some. Short of rearchitecting our service as a series of containers, what action can conscientious corporate leaders take?
If you prefer a more hands on approach just plain Xen or KVM is a great option too. As for orchestration in that space have a look at running Openstack or Xen Orchestra etc.
Re: VMWare Taken to Court Over GPL Violation
#39Any litigation of the GPL is more than likely more dangerous for the GPL than it is for the companies. A relaxing of the understood requirements of using and distributing GPL code could cause an avalanche of fall out from formerly protected code becoming less protected. If I was this organization I would only risk a lawsuit of something that would have profound positive consequences for open source. VMware's risk is…
This can only have a positive outcome. The alternative is the GPL ceases to exist.
Re: VMWare Taken to Court Over GPL Violation
#40So this could be really interesting from a precedent standpoint because it could help clarify the legality of the GPL in various contexts in the court. Whatever you think about the GPL (and I'm for open source and open licenses but I do have issues with GPL v3, but that's just me), this has been necessary, I believe, in order for GPL and OSS projects to move forward.
I'm not sure it will be that groundbreaking; this seems to be yet another busybox violation litigated in Germany, of which we have had several already.
LWN has some more detailed coverage, describing the proprietary vmkernel component that gets loaded into the kernel as a kernel module, and the specific files from the kernel that are included in this: http://lwn.net/SubscriberLink/635290/d7304b50a2ef15b0/
This is much deeper than simply a binary kernel module that uses the exported interfaces; it also appears to copy wholesale large parts of kernel internals, not just access the kernel via defined interfaces.