06.06.07
Any Meat to That Fruit? (Updated)
Kevan Barney posted an update on Novell’s PR blog the other day touting an available SLES VHD file for Microsoft’s Virtual Server as "More fruit from Novell’s collaboration with Microsoft":
More fruit from Novell’s collaboration with Microsoft … Novell has made available SUSE Linux Enterprise Server on Microsoft’s Virtual Hard Drive (VHD). The VHD image file contains SUSE Linux Enterprise Server 10 Service Pack 1 with most available packages already installed. With this image, folks can run SUSE Linux Enterprise Server 10 SP1 on their Microsoft Virtual Server 2005 R2 and experience Linux easily and risk free. Check it out.
So, I was a bit intrigued - after all, virtualization cooperation (and requisite patent licensing) is one of the areas of collaboration publicized in the Microvell deal - as Stafford Masie said - "Yes, there is a competitive angle there, yes we’re coming at VMware yes yes yes we are".
So, I asked - what about this was made possible by the Microvell deal, and I took the opportunity to link here to an article regarding how Novell has licensed certain Microsoft patents in order to build a binary bridge for Microsoft Windows to run on (SUSE) Linux. My implied question is whether a license is somehow required to implement virtualization in Microsoft products, but anyhow.
What I received was an explanation regarding hypervisor vs non-hypervisor solutions and some gobbledygook about "The SUSE Linux Enterprise Server 10 VHD enables customers using Microsoft Virtual Server to easily check out SLES10." but still - no answer to my (real) question - what, exactly, about this is “fruit” of the Microsoft collaboration? What made this impossible before the deal, is there a technical improvement - or is it licensing related after all?
We’ll be waiting for Kevan to clear this up, I have a feeling that there is absolutely nothing to do with the collaboration with Microsoft here, but rather was just a vain attempt to credit the deal for a coincidental occurence. We’ll see…
# shane coyle Says: Your comment is awaiting moderation.
June 6th, 2007 at 1:09 pmThanks, I know that really - I was making a point, but anyhow - what, exactly, about this is “fruit” of the Microsoft collaboration?
What made this impossible before the deal, is there a technical improvement - or is it licensing related?
Update: Here is the latest…
# Kevan Barney Says:
June 6th, 2007 at 4:09 pmShane,
It’s fruit from the collaboration between Novell and Microsoft because before we began collaborating, it simply didn’t exist. Now we’ve worked together to make it happen.
——-
# shane coyle Says: Your comment is awaiting moderation.
June 6th, 2007 at 7:11 pmSo, then this is the fruit of a wide ranging collaboration and licensing agreement with EMC/VMware?
Highlight: Novell was the first to acknowledge that Microsoft FUD tactics had substance. Novell then used anti-Linux FUD to market itself. 
Highlight: Xandros let Microsoft make patent claims and brag about (paid-for) OOXML support. 
Highlight: Linspire's CEO not only fell into Microsoft arms, but he also assisted the company's attack on GNU/Linux. 
Highlight: Microsoft craves pseudo (proprietary) standards and gets its way using proxies and influence which it buys. 
Highlight: The invasion into the open source world is intended to leave Linux companies neglected, due to financial incentives from Microsoft. 
Analysis: Xen, an open source hypervisor, possibly fell victim to Microsoft's aggressive (and stealthy) acquisition-by-proxy strategy.