On Wed, Aug 31, 2011 at 07:49:14PM +0200, Stefan Seyfried wrote:
Hi Greg,
Am Wed, 31 Aug 2011 08:41:42 -0700 schrieb Greg KH <gregkh@suse.de>:
vmware has worked to get their code accepted into the main kernel.org repositories, while virtualbox refuses to get involved at all and the community is tired of seeing bug reports like "virtualbox doesn't compile on the latest kernel" when there is nothing that they can do about that at all.
So why does vmware apparently not compile with every new kernel that's out there? Not that I'm using it, but every second week someone comes up and asks for help compiling some VMware modules, so there hast to be some problem :-)
Because they are usually using an old set of the vmware out-of-tree modules for a different vmware product than the most recent one.
And apparently at least the latest vbox version is quickly fixed for new kernels.
Hopefully, but I've seen enough bug reports to know this isn't always the case :( Anyway, I was just trying to explain why the kernel developers like vmware more than virtual box. Oh, then there's the code base itself, don't get me started on what the virtualbox code looks like... thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org