Pass the smelling salts.

Microsoft Monday released 20,000 lines of device driver code to the Linux community under the GPL 2 license, the mother of all open source licenses written when open source was still a pup by the brassbound Free Software Foundation.

The company itself admits the shock, horror move “would have been unheard of from Microsoft a few years ago” and puts it down to customer demand.

According to Tom Hanrahan, director of Microsoft’s Open Source Technology Center, “Customers have told us that they would like to standardize on one virtualization platform, and the Linux device drivers will help customers who are running Linux to consolidate their Linux and Windows servers on a single virtualization platform, thereby reducing the complexity of their infrastructure.”

In other words, Microsoft is sacrificing its religious convictions to its pocketbook. (Pshew, no apostasy there then.)

The recession, tight customer budgets, hardware consolidation and the realization that reduced complexity translates into reduced cost is forcing Microsoft to be more amenable.

According to Sam Ramji, senior director of Microsoft’s platform strategy, “We are seeing interoperability as a lever for business growth.”

The code, which includes three Linux device drivers, has been submitted to the Linux kernel community for inclusion in the Linux tree.

That’s another first. Microsoft has never released code directly to the Linux community before.

Barclay’s Capital thinks Microsoft’s unexpected move is aimed at VMware, which also provides drivers for Linux VMs to run on its ESX hypervisor. But because VMware’s drivers aren’t open source, the widgetry can’t be incorporated into the Linux kernel and IT admins have to do a separate installation.

Microsoft’s drivers will be available to both the community and customers, and are supposed to enhance Linux’ performance when virtualized on Windows Server 2008 Hyper-V or Windows Server 2008 R2 Hyper-V.

Hanrahan says, “Our initial goal in developing the code was to enable Linux to run as a virtual machine on top of Hyper-V…The Linux device drivers we are releasing are designed so Linux can run in enlightened mode, giving it the same optimized synthetic devices as a Windows virtual machine running on top of Hyper-V. Without this driver code, Linux can run on top of Windows, but without the same high performance levels.”

In a prepared pitch, Ramji suggests that Microsoft going forward means to make increased “use of ‘inbound’ open source and the open source development model to make our software development processes more efficient” and “to reduce marketing and sales costs or to try out new features that highlight parts of the platform customers haven’t seen before.”

Barclay’s thinks the drivers will show up in the primary kernel release scheduled for December.

Red Hat’s legal people figure Microsoft, which as they say previously regarded Linux, open source software and the GPL as the “axis of evil,” has “evidently accepted the reality that copyleft licensing is here to stay” but insist that it must now “pledge that its patents will never be used against Linux or other open source developers and users.”

One of Microsoft’s lawyers blogged back and told Red Hat very nicely not to hold its breath. “Taking purely ideological positions does not work in real life,” he said. “Instead, flexibility and nuanced approaches to complex problems will tend to win the day over dogmatic approaches.”

Separately, Microsoft has also released a free Live Services plug-in, also licensed under the GPLv2, to integrate its Live@edu services with the popular open source Moodle e-learning course management system.

See http://www.microsoft.com/presspass/features/2009/Jul09/07-20LinuxQA.mspx.

Microsoft’s not ready to punch out Google’s lights and ensure that Google Apps only appeals to people morbidly disaffected by Microsoft.

Contrary to rampant speculation the only thing Microsoft was prepared to say at its Worldwide Partner Conference this week was that its lightweight Office Web versions of Word, PowerPoint, Excel and OneNote are coming but not here yet. They’ll be available to select testers next month.

When they’ll be available period is still a mystery maybe even to Microsoft. It will only say that Office 2010 and “related products” will be out in the first half of next year. Of course there’s been a rumor Office 2010 would be out with Windows 7 in October.

What Microsoft did say was that when the Web apps get here they’ll be available in three ways: free to the 400 million consumers who already have Windows Live accounts; on-premises to all Office volume licensees including Microsoft’s 90 million or so Office annuity customers at no extra cost; and as a paid subscription hosted by Microsoft Online Services.

Microsoft didn’t say how much a subscription would be or what, if any, differences there would be between the free – potentially ad-supported – apps and the subscription apps.

When prodded, it said functionality would be consistent across the three platforms but that it was “too early to discuss final features and capabilities.”

It promises though that the Office Web applications would “provide access to documents from virtually anywhere and preserve the [desktop] look and feel of a document regardless of device.”

The Web apps are expected to support IE, Firefox and Safari and have more functionality than Google’s apps.

What they won’t be able to do is function offline the way Google can compliments of Google Gears. That will take the desktop version presumably to protect Office’s revenue model.

With SharePoint Workspace (the old Ray Ozzie Groove), Microsoft says you can synchronize SharePoint libraries and lists to your desktop, take it offline, make changes, and then when you’re online again the changes will automatically synchronize back to the SharePoint.

The widgetry should be able to save documents and files but printing is currently limited to the Word Web application. The other Web apps depend on the browser’s print functionality while co-authoring is only available in the Excel and OneNote Web apps so far, Microsoft told us.

Anyway, the desktop version of Office 2010 has gone into a pre-beta technical preview for testing by an invited group of “tens of thousands.” Microsoft said all attendees of this week’s conference would be invited.

Ditto Visio 2010.

There will reportedly be a proper beta later this year.

Microsoft also said it’s going to reduce the number of desktop Office editions from eight to five to ease purchase decisions and each would have additional applications and features like cut-and-paste preview for Word, Sparklines for Excel, video editing and voice annotations for PowerPoint, “ignore thread” for Outlook and collaboration all round.

Office Ultimate, Enterprise and Small Business will be gone leaving Professional Plus and Standard for the enterprise and Professional and Home and Student for everybody else. A new Home and Business edition will replace Small Business.

And there will both 32- and 64-bit versions for the first time.

Home and Student will include Word, Excel, PowerPoint and OneNote. Home and Business will add Outlook to the mix while Professional adds Outlook, Access and Publisher.

Standard includes Word, Excel, PowerPoint, OneNote and Publisher. Professional Plus adds Access, InfoPath, SharePoint Workspace and Communicator instant messaging.

There’s no pricing on any of this stuff yet.

The business unit responsible for Office brought in revenues of $4.5 billion in the March quarter, more than any other Microsoft division. The free software is expected to make a dent in the business, but it’s necessary for Microsoft to do the cannibalizing itself rather than give would-be competitors free rein.

Of the myriad web-based productivity apps currently on offer like Adobe.com, the only ones that matter at this point are Google’s and Zoho’s and they don’t look too threatening.

Zoho claims 1.8 million users and says 15%-20% of them pay. It won’t disclose revenues.

Google claimed last week that 1.75 million companies are using Google Apps, but it’s unclear how many seats that represents or whether all of them pay Google’s annual price of $50 a head. Supposedly 15 million people use the free versions but again it’s unclear whether that’s just sometimes, all the time or what.

Forbes says that IDC is trying to pull together some data on web apps.

Google ripped the beta labels off Gmail, Google Docs, Google calendar and Google Talk last week explaining that they communicated “not yet ready for prime time” to business accounts and were limiting their adoption.

Evidently Google was anticipating a more substantive move by Microsoft.

In response to Microsoft’s very limited announcement Zoho reacted with a statement saying, “What we see here is more evidence of Microsoft’s strategic muddle: how far do they want to go with their online offerings? They clearly recognize the risk – almost $16 billion in revenue (and almost the same in gross profit) is involved here, one of the largest franchises of software. We do not believe the $16 billion in revenue/profit is defensible, but our guess is that Steve Ballmer does not want to be the CEO who gives that news to shareholders. Not when the other multibillion [dollar] franchise is also looking a bit wobbly.

“Therein lies the fundamental dilemma for Microsoft and the fundamental opportunity for players like Zoho. What are considered crown jewels on the desktop today will become features to be integrated into a variety of business applications, and not on fat clients, but on the web. That is how we see the mail & office suite evolving – they become so nicely componentized (and affordable!) that they get integrated into every business application. A lot of what we are working on at Zoho involves such integration effort, both within the Zoho suite as well as with a lot of partners.

“One word captures this process: commoditization. Commoditization of their core cash cows is what Microsoft fears most, yet, we believe it is utterly unavoidable. Today’s announcement does nothing to address that basic fact.”

Google’s not the only one spouting the old Netscape line about the browser as platform or trying to evolve it into an operating system that can support an increasingly sophisticated web environment. Microsoft, which has yet to dignify word of Google’s proposed Chrome OS with a response, has similar ideas.

As part of a long-term project meant to bring web applications into functional and quality parity with desktop apps, Microsoft Research has been working on a browser code named Gazelle that it will describe next month at the Usenix Security Symposium in Montreal.

Microsoft says it’s the first time a browser has been implemented as a so-called multi-principal operating system but insists it’s just research, not a product prototype.

In browser-speak a principal is the owner/provider of a web page, script, widget, plug-in, frame, document or Web Service. So multi-principals are web pages that consist of content from different principals, each demanding resources that are unmanaged because the traditional browser’s not up to it.

That means “an ad containing malicious or poorly written code could hog the network connection, degrade performance, freeze the entire page, or crash the browser.”

But “in a browser operating system, a ‘bad’ principal would not be allowed to affect other principals, the browser, or the host machine.”

Gazelle’s kernel – 5,000 lines of C# code – is an operating system that “exclusively manages resource protection and sharing across web site principals.”

In Microsoft’s history of creation, “Web browsers originated as applications that people used to view static web sites sequentially. As web sites evolved into dynamic web applications composing content from various web sites, browsers have become multi-principal operating environments with resources shared among mutually distrusting web site principals. Nevertheless, no existing browsers, including new architectures like IE8, Google Chrome and OP, have a multi-principal operating system construction that gives a browser-based OS the exclusive control to manage the protection of all system resources among web site principals.”

Microsoft says “this construction exposes intricate design issues that no previous work has identified, such as legacy protection of cross-origin script source, and cross-principal, cross-process display and events protection.”

It believes its prototype implementation “indicates that it is realistic to turn an existing browser into a multi-principal OS that yields significantly stronger security and robustness with acceptable performance and backward compatibility” with existing web applications.

“In the Gazelle model, the browser-based OS, typically called the browser kernel, protects principals from one another and from the host machine by exclusively managing access to computer resources, enforcing policies, handling inter-principal communications, and providing consistent, systematic access to computing devices.”

It puts each principal including plug-in content in a separate protection domain by using an OS process.

The hard part’s evidently dealing with the “cross-origin” elements embedded in a web site.

Microsoft says “Gazelle’s architecture cleanly separates between the act of rendering Web content and the policies of how to display the content. This cross-principal display protection is in stark contrast to commodity browsers that enable these two functions to intermingle, leading to security vulnerabilities.”

Microsoft’s got a white paper called “The Multi-Principal OS Construction of the Gazelle Web Browser that claims Chrome (the browser) isn’t granular enough (see http://research.microsoft.com/apps/pubs/default.aspx?id=796550 .

From what little is known, Gazelle seems a whole lot different than the Chrome OS, which sounds like it’s been created by grafting a conventional browser application (Chrome) onto a conventional operating system (Linux) in a more tightly integrated way than the current combination of IE and Windows.

Gazelle, on the other hand, is being designed as a fundamentally new kind of browser that functions as a true operating system for web-based content and applications that can (theoretically) run on top of any machine-level operating system.

Gazelle is not a new version of IE. In fact, it has two parts, a browser instance, which in the current version of Gazelle is IE8, and a browser kernel, which is the new “operating system” part.

In spite of the fact that Gazelle introduces many new capabilities over conventional web browsers, it has a primary design goal of enabling full backward compatibility with existing web content and functionality, allowing managed, phased adoption by developers and content providers.

Gazelle’s architecture and design yields several advantages over Chrome, IE and all other browsers. (NB: Opera is excepted for plug-ins, but at some performance cost versus Gazelle.)

It introduces numerous technical innovations to address the Big Three vulnerability types that currently plague Chrome and other browsers: display objects, plug-ins and cross-origin content.

It manages system resources and browser processes in a different, more fine-grained way than Chrome and other browsers. As a result, for example, an undisplayed tab page won’t take resources from the one the user is currently using.

It appears that what Windows, Mac OS and Linux are to executable programs, Gazelle is to Web Services.

Think about it. A single interactive web application, like a shopping portal or social network, usually comprises many different Web Services for presenting content, making transactions or whatever. Each individual content element or Web Service on a page or in an application might be technically “owned” by a different site or company, but Chrome doesn’t see it that way.

Chrome considers the sites that share the same registrar-controlled domain name to be from the same site, so ad.datacenter.com, user.datacenter.com, and datacenter.com are considered to be the same site and belong to the same principal. In contrast, Gazelle considers them to be separate principals.

When a site, say a.com, embeds another principal’s content, say an <iframe> with source b.com, Chrome puts them into the same site instance. In contrast, Gazelle puts them into separate principal instances.

By resolving content and service ownership down to this elemental level of granularity versus Chrome, Gazelle

•    reduces the design, implementation and support overhead of  multi-source content;
•    enables richer models for providing, presenting and monetizing content and services;
•    and limits or eliminates inherited risk, cost, and liability from faulty subordinate components.

The shoe that Google’s been itching to drop – the one everybody knew was dangling – has finally dropped.

With Pearl Harbor-like timing of a declaration of war, Google VP of product management Sundar Pichai and engineering director Linus Upson said in a midnight blog post Wednesday morning that Google’s going to develop a fast, lightweight, open source operating system based on its nine-month-old Chrome browser to compete against Microsoft.

The so-called Chrome OS, described as Chrome running in a new windowing system on top of a Linux kernel, won’t be ready for prime time until the second half of 2010, a lifetime in Internet minutes.

The schedule gives Microsoft, which is busily detaching its browser from its operating system in Europe, plenty of time to figure out how to retort if it doesn’t already have a plan other than Windows 7.

Google’s aiming to put the thing on ARM- and x86-based netbooks first and sometime after that on full-sized desktops, both places where Microsoft overwhelmingly dominates. Google says it’s working with “multiple OEMs to bring a number of netbooks to market next year.”

It later identified them as Acer, Adobe, ASUS, Freescale, Hewlett-Packard, Lenovo, Qualcomm, Texas Instruments and Toshiba.

As open source Google says Chrome OS will be free, a clear attempt to drain Microsoft’s treasury.

Chrome OS is not Android, the Linux-based operating system Google is pushing onto phones, although the two admittedly overlap since Android is also supposed to fit into netbooks.

Instead Chrome OS is described as a new Linux project that will be open sourced later this year so the community can contribute.

Google says existing operating systems, meaning of course Windows without saying so, were designed before the web was invented. The web and applications running in the browser – not the operating system – are central in Google’s thinking. Chrome OS is supposed to get the user onto the web in seconds via a minimal interface designed to stay out of the way.

The company says it will “completely” redesign the underlying security architecture to avoid viruses, malware and security updates. (Cookie-free might be more useful at this point but unlikely coming from Google.)

Google promises that all web-based applications will automatically work and any new applications written for the thing will also run on any standards-based browser on Windows, Mac and other Linux operating systems “to give developers the largest user base of any platform.”

Google uses Linux internally so it can presumably make an operating system robust enough to hold up. But netbooks are not the stuff of mission-critical work, Linux has so far failed to loosen Microsoft’s grip on PCs (not even on netbooks), and the Chrome browser has yet to make much headway against Microsoft or even the Google-subsidized Firefox.

By Google’s count it’s only used regularly by 30 million people, a relative rounding error.

Despite its talk of community development, which is probably more viral marketing than anything else, an operating system is also going to cost Google a pretty penny or two to extend, support and maintain. (Ask IBM. Its futile OS2 efforts cost it close to a billion dollars a year back in the day.) And Google might actually have to talk to people to support the thing, something it has no cultural skill at.

Heck, it might even have to learn how to write a press release – or talk to the press. A blog posting is not marketing.

The object of Chrome OS, aside from harrying Microsoft, which is trying to harry Google back with its new Bing search engine, is of course to sell more ads by driving traffic to Google Search and other Google “services.” It is not about getting work done.

The Guardian reckons Chrome OS will “strip whatever hardware it runs on of most of its usefulness, without actually reducing the price by very much.”

Tim Negris, the former IBM and Oracle VP who invented the expression “thin client” for Larry Ellison when Oracle and its pal Sun Microsystems – Google CEO Eric Schmidt’s alma mater – were pushing the initial concept of a cheap network computer, takes the Chrome OS for a poor play on that last century idea.

He gives Google “all props” for its success so far but calls the Chrome browser “a fat client in a girdle, sneakily sucking cycles off the plates of other (non-Google) apps” and says that “even if that weren’t the case, it will still probably make a crappy app platform. A largely stateless, page-oriented interface is not the best way to interact with most computer applications, other than stateless page-oriented ones like web sites. Windows, Linux and Mac OS (Mach Unix) are far from perfect and I am a big believer in the concept and manifest destiny of the thin client, but, for Google’s particular concept to work, the Internet itself must become an operating system, and not simply be a means of linking one operating system instance to another. Google is taking the web as we know it, including 2.0, as far as it can, but it’s not in a position to drive the changes needed to make the true always-on thin client a reality. That task is in the hands of Cisco, Akami and others who can make the connective infrastructure much smarter than it is today, and that is what it will take to make the endpoints as dumb and simple as Google would like them to be.

“The Plan 9 and Inferno distributed operating systems work that was done at Bell Labs some years back was a lot closer to the right approach than the dog’s breakfast of network computing being served up nowadays by Google, Microsoft, Apple, the Linuxes, Oracle and other ‘end point’ vendors. The Bell stuff was not perfect or complete by any means, and probably flawed in places, but that’s not why it didn’t go anywhere. Plan 9 was smothered in its crib and Inferno sent to a foster home by their impatient, unloving parents on the business side of AT&T. Google would do well to pocket its pride and reach out to people like Rob Pike, Ken Thompson, Dennis Ritchie, Brian Kernighan, Bjarne Stroustrup and others who know history well enough to avoid repeating it.”

Google is ratcheting up its challenge to Microsoft elsewhere too. Hours before its Chrome OS disclosure, it finally ripped those perpetual beta labels off Gmail, Google Docs, Google Calendar and Google Talk to appeal to a wider swath of the business set.

Maybe it’s just wishful thinking on our part, but it sounds like Microsoft – in the very nicest way, of course, to avoid any further fines – just told the European Commission to go fuck itself.

See, at press time Thursday, CNet was saying that it saw a confidential memo that Microsoft sent to OEMs and that Microsoft plans to ship Windows 7 in Europe without its browser at all leaving it to the OEMs to put it back in complements of a free “IE8 pack,” ship a different browser or ship a bunch of browsers.

There will be no version that includes the browser either through OEMs or through retail.

The retail consumer will have to get IE via CD, FTP and somehow.

The move, which would throw a monkey wrench into upgrades, would deny its rivals a free ride on Windows. The OEMs could sell the space for a king’s ransom. Firefox and Opera couldn’t afford it. Apple could care less. And Google could ante up.

Faced with the logical conclusion of its own logic, the EC – which remember is supposed to be protecting the consumer – reportedly said that it “had suggested to Microsoft that consumers be provided with a choice of web browsers. Instead Microsoft has apparently decided to supply retail consumers” – roughly 5% of the total – “with a version of Windows without a web browser at all. Rather than more choice, Microsoft seems to have chosen to provide less.”

It also reportedly said, “As for sales to computer manufacturers, Microsoft’s proposal may potentially be more positive. It is noted that computer manufacturers would appear to be able to choose to install Internet Explorer – which Microsoft will supply free of charge – another browser or multiple browsers.”

The suggestion has Opera, which brought the original complaint, howling.

Microsoft’s deputy counsel has basically allowed on Microsoft’s legal blog that it may not get away with this. But it’s fun anyway, isn’t it?

Microsoft, Yahoo & Open Source

The watchtowers trained on the latest round of Microsoft-Yahoo talks on a search and advertising partnership report that they have finally become “meaningful” in the words of one source and could produce an actual contract in a few weeks.

AllThingsDigital, the key observation post, claims that the deal they’re talking about has Yahoo taking over search and recession-hit display ad sales and Microsoft building the search and display ad-serving technology for both of them. It also says Yahoo would be able to fire Microsoft if Microsoft screws up.

Now as it happens, Kumo, Microsoft’s next-generation search engine, which could debut early next month, uses Hadoop to generate its search index.

That should make Yahoo feel right at home considering Yahoo created the open source distributed computing platform based in turn on Google MapReduce widgetry and Powerset, the open source operation Microsoft bought last year that’s doing Komo, also ran up HBase, the open source knockoff of Google’s Big Table storage system.

The Register cracks that Komo will be the first product that Microsoft “ships” that’s based on open source. It’s not all open source of course. It also uses proprietary technologies like Xerox PARC’s XLE ranking algorithms.

Open Invention Network (OIN), the Linux-protecting patent-collecting consortium put in train by IBM and supported by NEC, Novell, Philips, Red Hat and Sony in the name of mutual deterrence, is whistling up the Penguinista brigade asking them to throw prior art at three Microsoft patents in order to knock them down.

Microsoft claimed the GPL 2-covered Linux kernel treads on three of its file management system patents when it sued TomTom, the Dutch GPS device maker, for patent infringement earlier this year.

A few weeks later – and despite a feeble countersuit and bold public statements – TomTom bent to Microsoft’s will and agreed to pay Microsoft an unspecified amount of money for five years’ worth of patent protection.

Microsoft claimed that the GPL-forbidden payment was constructed in such a way as to leave TomTom “fully compliant with TomTom’s obligation under the General Public License Version 2.”

It did not explain how.

The Penginistas obviously can’t let such a claim stand unchallenged since it opens the door for Microsoft to collect royalties on the Linux kernel more broadly.

So OIN has posted the three US patents – Nos. 5579517, 5758352 and 6256642 – on the Post-Issue Peer-to-Patent web site associated with its Linux Defenders portal for Penguinista quality review.

Meanwhile, Red Hat’s legal department put out a statement meant to get the Penguinistas’ blood boiling in case Microsoft doesn’t do what Red Hat really wants it to do and that’s to foreswear asserting its three patents against Linux.

Red Hat of course could be in real legal and financial jeopardy if Microsoft ever decided to pull the patent trigger.

So in between calling Microsoft names and threatening it with “counterattack,” Red Hat “challenged” Microsoft’s deputy general counsel Horacio Gutierrez to “publicly promise that the patents asserted in TomTom that are being addressed by OIN will not be used by Microsoft for patent aggression against Linux.”

Of course both Red Hat and its little friend OIN could be deceiving themselves about the vulnerability of Microsoft’s patents. Red Hat’s statement cites “numerous public reports” suggesting weaknesses in these patents. However, both ’517 and ’352 have already withstood re-examination by the Patent and Trademark Office. Both were issued in 1996 and reconfirmed 10 years later.

Anyway, OIN said prior art submissions could be made at www.post-issue.org.

The full text of Red Hat’s statement is at http://press.redhat.com/2009/04/28/some-sunshine-on-shadowy-patent-threats-a-reaction-to-microsoft-v-tomtom.

The Linux kernel apparently does in fact infringe on Microsoft’s patents – at least that’s certainly the way it looks to the casual observer because TomTom has agreed to yank the offending widgetry out of its GPS devices over the next two years.

That’s part of the deal it made with Microsoft the other day that settles Microsoft’s patent infringement suit against the Dutch company and TomTom’s show countersuit.

TomTom is paying Microsoft an unspecified amount of money for five years’ worth of protection against the eight patents that Microsoft charged TomTom with treading on including the three file management systems (FAT) patents related to the GPL 2-covered Linux kernel.

And Microsoft gets covered but doesn’t have to pay for the four TomTom patents it was allegedly offending.

Microsoft claims that the way the patent coverage is constructed “is fully compliant with TomTom’s obligations under the General Public License Version 2” complements of a legal workaround, a variation on the Novell accord.

It said, “TomTom will remove from its products the functionality related to two file management system patents (the FAT LFN patents), which enables efficient naming, organizing, storing and accessing of file data. TomTom will remove this functionality within two years, and the agreement provides for coverage directly end customers under these patents during that time.”

In a statement Microsoft deputy counsel Horacio Gutierrez remarked that the FAT patents have been “licensed by many companies, including those that produce mixed source products.”

“We were able to work with TomTom to develop a patent agreement that addresses their needs and ours in a pragmatic way,” he said. “When addressing IP infringement issues, there are two possible paths: securing patent coverage or not using the technology at issue. Through this agreement, TomTom is choosing a combination of both paths to meet the unique needs of its business, and we are glad to help them do so.”

The episode was only the third time in its life Microsoft sued somebody for patent infringement and the very first time it took out after Linux although it has protested for years that Linux infringes on its IP.

Microsoft settled all three suits out of court. Before filing suit and complaining to the International Trade Commission in late February, Microsoft reportedly chased TomTom for over a year trying to get it to license its patents and so wanted treble damages.

Now the questions are whether the open source community will challenge the agreement and who’s next?

The Linux establishment was not well pleased.

Red Hat’s legal people waded in with the opinion that “without a judicial decision, the settlement does not demonstrate that the claims of Microsoft were valid.” TomTom, they contend, could have had other reasons for settling and without knowing the terms of the settlement, it’s impossible to say whether they comply with open source rules or not.

The Software Freedom Law Center put out a statement saying, “The settlement neither implies that Microsoft patents are valid nor that TomTom’s products were or are infringing.”

And what’s more it claims that Microsoft’s patent are invalid and promises to “act forcefully to protect all users and developers of free software against further intimidation or interference from these patents.”

It said that it and the Open Invention Network and the Linux Foundation would “participate in a coordinated, carefully graduated response on behalf of all the community’s members to ongoing anti-competitive Microsoft conduct.”

The head of the Linux Foundation Jim Zemlin accused Microsoft of recidivist FUD around Linux in a blog saying, “In the last several days Microsoft has shown that despite claims of acquiring a newly found respect for open principles and technology, developers should be cautious in believing promises made by this ‘new’ Microsoft. When it counts, it appears that Microsoft still actively seeks to undermine those technologies or standards that are truly open, especially when those technologies pose a significant threat to their business.”

At the risk of interoperability, he also said, “The Linux Foundation is here to assist interested parties in the technical coordination of removing the FAT filesystem from products that make use of it today.”

It’s unclear how he comes to the conclusion that the outcome of this case is “a testament to the power of a concerted and well-coordinated effort by the Linux industry and organizations such as the Open Invention Network, the SFLC and the Linux Foundation. This was not merely a typical David vs. Goliath story. This time David aligned itself with the multiple slingshots of the Linux community. Microsoft relented as soon as TomTom showed they were aligned with that community and ready to fight. The system is working.”

Microsoft has emitted a squeal of protest much like a stuck pig over a secret “Open Cloud Manifesto” that it says is quietly being handed around the industry seeking signoffs.

It doesn’t identify the author or authors of this manifesto – one would guess organized by IBM given some recent whispers coming from its direction – but figures its supporters are going to reveal themselves soon enough and is warning against them.

See, apparently Microsoft wasn’t asked to contribute to drafting the manifesto, which evidently lays down “principles and guidelines for interoperability in cloud computing.”

It says in a blog written by product management director Steven Matin, “We were admittedly disappointed by the lack of openness in the development of the Cloud Manifesto.”

And apparently the manifesto is a take-it-or-leave-it proposition with no room for Microsoft to maneuver.

According to Martin,“What we heard was that there was no desire to discuss, much less implement, enhancements to the document despite the fact that we have learned through direct experience.

“Very recently we were privately shown a copy of the document, warned that it was a secret, and told that it must be signed ‘as is,’ without modifications or additional input.”

Not that Microsoft doesn’t “love the concept.”

“We strongly support an open, collaborative discussion with customers, analysts and other vendors regarding the direction and principles of cloud computing,” he says.

The trouble is that while “large parts of the draft manifesto are sensible. Other parts arguably reflect the authors’ biases. Still other parts are too ambiguous to know exactly what the authors intended.”

Like the pot calling the kettle black, he says, “It appears to us that one company, or just a few companies, would prefer to control the evolution of cloud computing, as opposed to reaching a consensus across key stakeholders (including cloud users) through an ‘open’ process. An open Manifesto emerging from a closed process is at least mildly ironic.”

Martin thinks such a thing “should be created, from its inception, through an open mechanism like a Wiki, for public debate and comment, all available through a Creative Commons license” to ensure that the work is “open, transparent and complete.”

He also thinks that any standards effort shouldn’t be vendor-dominated and that “while principles can be agreed upon relatively soon, the relevant standards may take some time to develop and coalesce as the cloud computing industry matures.”

“After all,” he argues, “what we are really seeking are ideas that have been broadly developed, meet a test of open, logical review and reflect principles on which the broad community agrees. This would help avoid biases toward one technology over another, and expand the opportunities for innovation.”

Arguing for the “freedom to develop” innovations that would lower cost and increase utility, he says “freezing the state of cloud computing at any time and (especially now) before it has significant industry and customer experience across a wide range of technologies would severely hamper that innovation. At the same time, we strongly believe that interoperability (achieved in many different ways) and consensus-based standards will be valuable in allowing the market to develop in an open, dynamic way in response to different customer needs.”

For the whole rant see http://blogs.msdn.com/stevemar/archive/2009/03/26/moving-toward-an-open-process-on-cloud-computing-interoperability.aspx.

Well, it’s finally happened. Microsoft, which has only sued two other companies for patent infringement in its whole life, is exercising its patent rights over Linux and suing TomTom, the Dutch-based portable GPS device house, for ignoring its pleas to license its patents like other GPS system makers have.

Actually Microsoft is suing TomTom on eight counts of patent infringement, five of which have nothing at all to do with Linux. But the other three do and that’s what’s bound to make a big noise.

In fact Microsoft is trying not to make too big a deal of the matter and is issuing statements saying, “Open source software is not the focal point of this action. The case against TomTom, a global commercial manufacturer and seller of proprietary embedded hardware devices, involves infringement of Microsoft patents by TomTom devices that employ both proprietary and open source software code.”

That’s hardly the point.

For years now Microsoft has claimed – over the loud protestations of the Penguinistas – that Linux infringes on its IP but it has never substantiated those claims in any way. This is the first time it has put some meat on the bone or even identified some of its claimed IP.

Besides filing suit Wednesday in federal court in its hometown of Seattle, Microsoft also took its case to the International Trade Commission (ITC) in D.C. asking that TomTom’s Chinese-made widgets be barred from U.S. shores.

It accuses TomTom of both direct infringement and induced infringement.

The stubby lawsuit is a dry, colorless affair that never mentions Linux; the 25-page ITC complaint, even in its redacted form, is more substantive. And the three “Linux” patents are the core of its complaint.

According to Microsoft’s story it has been chasing TomTom for over a year trying to get it to license its patents. That’s why its suit demands treble damages for willful and deliberate trespass.

The three provocative Linux-involving patents that Microsoft says TomTom is treading on are U.S. patents 5,579,517 and 5,758,352 both entitled “Common Name Space for Long and Short File Names” and 6,256,642 entitled “Method and System for File System Management Using a Flash-Erasable, Programmable, Read-only Memory.”

Microsoft explains to the ITC that TomTom’s GPS widgets run a version of Linux and that Linux “and/or the software applications supported by the operating system also provide the devices with additional functionality such as file system support for long and short file names, memory management for flash memory commonly used on such devices, and a platform for integrating and controlling various electronic components used with the portable navigation computing devices, such as other components in a vehicle.”

Microsoft says patents ‘517 and ‘352 “describe an innovative system that both supports long file names and maintains compatibility with file name system and applications that are aware of only short file names” so “a short file name system can read the directory entry containing the short file name but will ignore the directory entry (or entries) containing the long file name. A long file name system can access and manipulate these long file names and so in such a way as to ensure compatibility with the short file name system.”

Microsoft also explains that “file systems are the part of an operating system that manages files on a storage device. A common way of managing files is to use a hierarchical structure, often referred to as ‘folders’ or ‘directories.’ These directories contain files and often other directories or subdirectories. These traditional file systems were designed for ‘multiple-write’ devices rather than ‘single-write’ devices such as flash memory. The ‘642 patent describes a file system that supports the byte-addressable and block-erasable nature of flash memory, while providing support for a file system offering the functionality of traditional file systems.’

Microsoft says it uses ‘517 and ‘352 in Vista and XP (remember FAT16?) and ‘642 is used in Windows CE.

Microsoft also tells the ITC – in case the open source community thinks it’ll just get the patents declared invalid – that both ‘517 and ‘352 withstood re-examination by the Patent and Trademark Office. Both were issued in 1996 and reconfirmed 10 years later. Patent ‘642 dates to July of 2001.

There appear to be both Canadian and German counterparts to ‘517 and ‘352 that Microsoft has challenged.

TomTom declined to comment initially and then finally confided to Reuters that it rejected the claims and would “vigorously defend” itself.

Microsoft settled the two other patent infringement suits it brought out-of-court.-

© 2012 LinuxGram Suffusion theme by Sayontan Sinha