Embrace and extend: That has been Microsoft's competitive mantra for as long as I can remember. So it comes as no real surprise to me that the company would choose to release, via the GPL, device driver code that more closely integrates Linux into the Microsoft virtualization ecosystem. After all, it's not like Linux will be running the show in this relationship. Rather, it's making the FOSS (free open source software) community's fair-haired boy feel more comfortable as it settles into the warm, fatal embrace of Hyper-V that is the Redmond giant's ultimate goal.
Make no mistake: This is a hostile action on Microsoft's part. Its stated mission is to squash Linux like a bug, and the easiest way to do that is to feign friendship -- to offer a bogus olive branch, then switch it out at the last minute for a nasty bundle of thorns.
[ InfoWorld's Galen Gruman suggests why businesses should adopt desktop Linux instead of Windows. | And Neil McAllister asks if desktop Linux missed its chance ]
Don’t believe me? Ask IBM. As a consultant to the Software Solutions (SWS) group in the mid 90’s, I saw firsthand how Microsoft embraced IBM’s legacy architecture – through SNA Server and similar integration plays – and then swallowed the company’s mid-range business whole through a well crafted commodity power play.
Or talk to Novell. The onetime networking leader sat helpless as Microsoft embraced the IPX protocol, giving it equal time with its own NetBEUI (and thus neutralizing protocol choice as a factor) while quietly shifting its core development to the more level playing field that was TCP/IP.
Now, it's the FOSS community's turn in the Microsoft death grip. Watch as the Redmondians wax poetic about "co-opetition" and how they need to acknowledge customer demand for Linux-based solutions. Meanwhile, their real play is to gain control over the FOSS platform's implementation by obviating the need for non-Microsoft tools and frameworks. Then, when they've eliminated the last vestiges of Linux's pre-embrace existence, they'll slowly squeeze the life out of their now hapless victim by shortchanging it in new Microsoft platform releases and generally making the FOSS solution cost-ineffective.
This whitepaper explains the terminology and concepts behind Data Replication technologies and establishes some sizing rules through worked examples. Learn the new paradigm in disaster tolerance—protect data anywhere.
Download now »Server virtualization is a popular option for dealing with mounting datacenter costs. Another equally promising approach is the use of an Application Delivery Controller. Citrix NetScaler provides a low-cost way for organizations to reduce their server count and accrue cost savings from a reduction in space, cooling, power and personnel.
Download now »
The emergence of WLANs has created a new breed of security threats to enterprise networks.
Included in HP ProCurve WLAN solutions is security technology that alleviates threats from WLANs through:
* Monitoring wireless activity inside and out of the enterprise
* Classifying WLAN transmissions into harmful and harmless
* Preventing transmissions that pose a security threat to the enterprise network
* Locating participating devices for physical remediation
Effectively address data protection challenges, implementing solutions that help store and protect businesscritical data while cutting costs and improving efficiency and reliability.
Download now »bobburns, I'm afraid you're making two errors above. (Please note that the arguments below are my lay opinion -- I am not a lawyer.)
First, "GPL" is not a company, it's a legal contract. A person or company would have to do the suing.
Second, I believe GPLv2 has two clauses that would prevent Microsoft from using their own free Linux drivers for a proprietary new version. Section 2 forbids anyone using GPLv2-released code from modifying it and then NOT releasing it under the same, free-of-charge terms in this license. Section 7 says that if any GPLv2-licensed code includes non-free parts, the GPL'd code cannot be distributed -- period. (In other words, if you use GPLv2 for some code, you either distribute it legally for free, or not at all at any price. Richard Stallman calls this the "Liberty or Death" clause.)
I'm supposing that if Ballmer & co. don't use both a clean-room development of replacement drivers and a patented technology that no one could replicate without a license, then open-sourcers could modify the old code to make it work with this hypothetical new Hyper-V. If Microsoft tries to modify the old code to create new proprietary drivers, then they would make their own code illegal under Sections 2 and 7 unless it's also free-as-in-beer.
Rather than someone suing Microsoft, what might happen would be that anyone who could get their hands on the actual new source code could then freely implement the new drivers (since it must also be GPLv2-licensed). No license would be needed, no matter what the source code or Microsoft says. (Of course, I wouldn't want to be the one trying that without a big-pockets company to pay the lawyers to argue the case.) If Microsoft creates an entirely new, clean-room version, the FOSS community could modify the old code to catch up to it. But if the 'Softies throw in some new, patented software technology with a restricted license, open-sourcers could not legally create a functional equivalent without a (likely expensive) license from Microsoft. Again, I'm no lawyer, but that's the path I see for Microsoft to do their usual embrace, extend, and extinguish.
I am going to leave the World Domination theory along and just point out the following:
1. Making Linux work better under Hyper-V theoretically hurts VMWare more than Linux. If VMWare runs Linux MUCH better than Hyper-V, Microsoft does gain market share on VMWare.
2. The reason that Microsoft bested Novell (and I was doing Novell back in the 2.x and 3.x days) was that the NT File Server (which wasn't as good of a File Server as Novell) was a MUCH better application server (just ask anyone who has tried to develop a CPU intensive NLM program). Also, Novell tried ?nix back in the day, remember they were in bed with Unix at one time. They just didn't push that and also were trying the antithesis of the Open Source model with ?nix, and that did work (just ask SCO).
3. IBM's problem with midrange was that their hardware is way to expensive (even Apple has figured that one out). When everything costs twice as much, the cheaper stuff, as long as it is decent will win out. AS/400 and IBM Unix will always be a niche market, but never high volume.
I don't disagree that Linux should be a little wary about Microsoft, but Linux will succeed or fail based on it's own merits (and most likely only if they can control the fragmentation and the lack of a good common application packaging and distribution model) such as ease of use.
Microsoft providing drivers that makes Linux run better on Hyper-V is the very LEAST of Linux's things to worry about.

Sign up to receive InfoWorld Resource Alerts

1 reply
Randall
You are so right, I can't agree more!
What is Microsofts stock Symbol again MSFT?
Volome