On Thu, Jul 23, 2009 at 2:12 PM, Paul Saenz<[email protected]> wrote: > Even though the motivation is a purely selfish one, is there anything wrong > with that? Microsoft certainly plans to “outsmart open source” and this move > should be seen in that light, but at the end of the day they are doing the > unthinkable - contributing to free software - and that’s a win. > I agree with Linus here where he says that M$ certainly plans to "outsmart > open source" and this move should be seen in that light.
Outsmart open source? Care to enlighten here? I'm not sure I follow your line of thought. > I hope Linus has enough sense to leave it out of the kernel, and just allow > it as a module that individuals can install themselves, and I hope the > different distributions also leave it out of their distribution. Just let > people install it who need it. Why leave it out of the kernel? Bear in mind you can always recompile your kernel and include/exclude whatever you want. I think code like this should be readily/easily available to be compiled into the kernel on any installation. Just because something is included in the kernel tree doesn't mean that it's compiled into the kernel by default. Ultimately, this boils down to their battle with VMware for hypervisor market share, and they wouldn't be able to make a move without having similar or better support for Linux guests compared to ESX. This is where this code comes in handy. I think it's an excellent approach, even though it's for their own benefit, but at the end of the day, the code is open and benefits anyone that decides to put a Linux guest in a Hyper-V host. -Dante
