On 05/01/2015 09:06 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-05-02 03:29, Michal Kubecek wrote:
On Sat, May 02, 2015 at 03:19:02AM +0200, Carlos E. R. wrote:
And then there are other proprietary blobs with no alternative at all. The obvious case is virtualbox or vmware, but there are more.
Not sure which modules you mean here. Both host and guest VMware modules are provided with their source and this source is used to build the modules if you don't have one of the kernels for which pre-built modules are provided (I never had). Actually, some of their modules that used to be out-of-tree have been merged into mainline kernel (vsock, vmw_vmci).
Sometimes the kernel changes "too much" and the vmware module refuses to build (during install of vmware, it builds things automatically). With luck, some one publishes a patch that you have to apply manually, and it works. Then someone writes a script. And, maybe six months later, vmware publishes a new version that handles the kernel change properly.
This has happened several times in the past. It even happens with stable openSUSE releases, which is a reason to not install it till after a few months...
When a kernel API changes, vmware is a lot slower than virtualbox to implement those changes. When kernel 4.1-rc1 was released and symbol IRQF_DISABLED was no longer defined, VB had a fix available in days. I had already found and fixed the problem, but I did not bother to submit it to Oracle as I knew they would have already had the patch in testing. Larry -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org