Introduction About Site Map

XML
RSS 2 Feed RSS 2 Feed
Navigation

Main Page | Blog Index

Archive for the ‘Novell’ Category

Novell and Sun Make a Deja Vu

Shortly after the infamous deal had been made, I happened to have spotted an article about Sun’s deal with Microsoft. It goes back to 2004.

Microsoft Corp. on Wednesday said that it is looking for ways to work more closely with developers of the Open Office open source project, while at the same time, apparently reserving the right to sue them, according to a legal agreement between Microsoft and Open Office’s major sponsor, Sun Microsystems Inc., made public this week.

PJ has just posted the following analysis. It compares Novell’s deal with Sun Microsystems’ deal.

What do I think Microsoft is doing with these deals? I suspect they are making deals with every entity that has patents, clearing the deck so it can attack Red Hat and the entire Open Source method of development. Whatever is left standing will be firmly inside Microsoft’s embrace, and you know as well as I do what that historically means.

The way this is bound to develop will be interesting for many reason. Among those reasons we have OpenOffice, which is fundamentally the main link between the two deals. While the OpenOffice team approves and supports the deal, Novell can be scrutinised over that very same legal timebomb.

Will SUSE Become Yesterday’s Distro?

According to Bruce Perens, one ought to expect SUSE to incorporate outdated packages or face some hard financial dilemmas.

“In the face of these [GPLv2 to GPLv3] changes, Novell will probably be stuck with old versions of the software, under old licenses, with Novell sustaining the entire cost and burden of maintaining that software,” Perens wrote, adding that Novell faces a choice of sticking with Microsoft and being left behind, or turning its back on the patent deal.

Matt Asay goes further and mocks Novell’s judgment.

Again, if Microsoft’s patents are only worth $40M or so, and Novell’s are worth $300M, then does anyone have anything to fear about Microsoft’s patent rattling? If their value is comparatively worthless, why is anyone bothering to take them seriously (this assumes, of course, that someone is)?

This confirms what many people argued before. The sums appear nonsential, which leads to suspicion that the motives go beyond what meets the eye. Microsoft’s legal department is nothing to sneeze at and, quite evidently, Novell has been fooled. It’s time to escape the deal (to the extent possible) and save SUSE before it’s too late.

The recent Open Letter/petition illustrates the fact that a lot of damage has already been done and continues to be done at present, primarily because the management is reluctant to admit its mistake. The intention of this site is not to religiously bash and damage Novell, but rather to knock it back into its senses, rather than let it be driven to a state of bankruptcy. Pressure might be the only path to remedy.

Time for Microsoft and Novell to Depart

Don Parris of LXer.com recently did an interview with itbusinessedge.com. Therein he suggests reversing parts of the deal that are concerned with patents protection. The interview closes with the following statement:

Both parties need to re-think this… What bothers me most about the agreement is that Novell seems somehow caught off guard by Ballmer’s words. Did they not know Microsoft’s position going into the deal? Novell should have reasonably known that Microsoft would use this deal to try to scare people into cutting deals with them — and maybe that’s the real benefit for Novell. If Microsoft believes [the Linux] community’s code infringes [its] patents, why don’t they send letters asking the respective coders to cease and desist? That way, the infringement can stop on amicable terms. Otherwise, Microsoft — especially Ballmer — needs to shut up.

Interoperability should have been the one and only aspect from which to gain. Microsoft’s advantage clearly came from subtle clauses, which opened to door to convenience in argumentation, e.g. pressuring Red Hat, the European Commission, and spreading unfounded FUD.

Your Mistake, Your Exclusion

The Novell/Microsoft deal may be the last straw in a sequence of mistakes which, over the years, have led to layoffs. The Inquirer takes a look at what it considers to be Novell’s top 5 mistakes. Here is the gist.

5. Not merging with Lotus.

4. NetWare Lite.

3. Ever-changing strategies.

2. Buying Digital Research.

1. Buying WordPerfect.

In another short writeup, I believe we see the term “Novellization” being coined.

Forget about Tivoization. How about adding a clause to the next version of the GPL that counters Novellization?

It is apparent that Novell is being excluded by the Free Software community inasmuch as it has aliented itself on November 2nd.

Selective Patching with Novell Exclusion

Nicholas Petreley of Linux Journal warms about the dangers of accepting patches from Novell.

It is with regret that I urge all FOSS developers to treat anything Novell has contributed to the community as suspect, scrutinize any Novell contributions and purge them as deemed appropriate.

As argued before, OpenOffice, Mono, and even Samba, whose developers strongly protested against this deal, are becoming a legal timebomb. Isolation from Novell is separation from Microsoft’s hands.

Mark Kent on Novell

It’s no secret that I mirror my contributions to another site and plant them in this blog. If this bothers long-time readers, please let me know.

Mark Antony Kent submits the following take on Novell’s deal:

“Presumably this deal really goes back to Novell’s roots. Their heritage is entirely that of a proprietary software vendor, who’ve been competing with Microsoft for at least a couple of decades, and mostly losing.

As things got really bad for Novell, the board was very aware that the only growth area which was not dominated by Microsoft was in free software, so they looked around to see what they could do. The most promising of all the distributions at that time was Suse, based in Germany (important – not in the US), had good traction in Europe and was well respected globally.

Like most of the early distributors, Suse was doing financially okay, but no more than that, and was desperate for cash to fund their continued expansion; working in a commodity environment means working with very very narrow margins, having significant investment can make that much less painful.

So, it looks like a match made in heaven. Novell, the well respected US-based networking company, investing in, indeed buying, one of the big four Linux distributors. Everyone in both the stock-markets and the open-source world applauded the move; Novell had a new lease of life in the server arena, their traditional market place, /and/ got to push Suse for the desktop too. Until Ubuntu came along, Suse was considered by many to be the most mature business desktop offering.

Unfortunately for all concerned, although the match was reasonably successful, and Novell have enjoyed a steadily increasing penetration into the desktop and server markets previously dominated by Microsoft and Unix vendors, the rate wasn’t all that high, and was damaged by the SCO activity, something Novell found itself on the wrong side of, but was acutely aware it was in the spotlight.

At about the same time, the FSF and Prof Moglen began work on GPL3. GPL3 is intended to prevent the last great legal threat possibility against linux and free software, that of patent fud. When the GPL was first created, this wasn’t much of an issue, because nobody had been granting patents for trivial software, but, the USPTO was made a profit centre, and its managers realised very quickly that in order to make their profit, so that they could get their bonusses, they must grant as many patents as they possibly can; which is what they did. Patents have been granted for such triviata as an “icon on a screen” to such obvious developments with prior art, such as moving email on a packet-radio link (RIM suffered from that one, even though it’s been going on for decades).

So, as the SCO debacle reached its peak, the FSF people were considering how to counter this new threat against freedom, albeit a threat resulting from a series of blunders by the US Government, including starting to offer software patents, and then making money from granting them. Thus, GPL3 is born.

The evironment in which GPL3 came to pass should be considered carefully, and compared with GPL2. For GPL2, most developers were freelancing in some way or other, perhaps paid by some employer, but their work wasn’t germane to the company, perhaps students or academics, or enthusiasts working at night in their cellars. Thus, GPL2 addressed their fears very well – their work could not be taken by anyone else, improved and sold-on, without the improvements being returned to the code base. A reasonable proposition, although even then, major companies such as Microsoft were already calling it a Cancer, precisely because they were not able to take the work and pass it off as their own.

By the time GPL3 is being written, though, free software has become something of a victim of its own success. Many, if not most, developers are now working for commercial organisations, or, if not, at least they’re working for “not for profits”. Thus the whole attitude to patents is affected, if not dominated, by the legal departments of their employers. The concepts of “RAND” – reasonable and non-discriminatory, are preferred licensing methods by many companies, based on the sage advice of their senior legal people. Why? Because they still do not understand how software is developed, or why free software has been so successful. There is still the view that free software can be “de-commoditised” in some way, although any economist worth his salt will tell you that this is exceptionally difficult to achieve (but not impossible).

So, whilst the previous generation of academics, cellar-dwellers, students and part-time coders were happy to have their own work protected by GPL2, the current generation are having to look over their shoulder at their legal team for GPL3, but their legal teams do not necessarily understand why GPL2 exists; they might understand what it means, but they don’t understand why its there. Thus, GPL3 is getting a rough ride indeed from many people. An additional argument has been that GPL3 is not the right route to resolving the software patent problem, indeed, it’s just possible that this is true, however, pragmatically, it’s likely to be the only one which will work, unless someone seriously believes that the free software community can take on and beat the US government on patents granting – something I doubt very much.

Microsoft have learnt a lot from their funding of SCO to claim copyright on Linux. These lessons include that the approach was, in fact, surprisingly successful. There’s always a pundit or analyst who can make money from selling the FUD on in companies, and as most companies, and lawyers, are naturally very conservative and cautious, merely making a public accusation can be enough to stop customers from moving to linux. However, the second lesson has been that whilst the wrath of the free software community doesn’t scare them one bit, the steady loss of customers to the free software world scares them greatly. They have no fear of the FSF, of Linus T, of ESR or of RMS, but they are terrified of linux distributions which prove that free software is good enough for most uses, and they’re terrified of the GPL, which protects them.

So, they’ve gone for a second round of legal attack. This is nothing new for Microsoft, indeed, the SCO case was nothing new. From the beginning, Microsoft have been about manipulating the legal system to their own ends, and marketing heavily to persuade an unknowledgeable public of their wholesome aims. The agreement with Novell is just one more step from Bill Gate’s original letter regarding the copying of basic, sent just scant months after he’d stolen printouts himself in order to write the basic, Microsoft have never played this game with anything less than four Aces up each sleeve.

Microsoft saw GPL3 coming along like a high-speed train, and they were struggling to get over the level-crossing. They knew that they had just a few weeks, months at most, to get a patent attack in, before the free software world began to recognise the huge danger this poses, so, they did one of the things they’re best at. They charmed the board of a company – in this case, a competing company, but one which they knew was still cash-strapped, was not growing at the rate it wanted to, and was still painfully aware of how close it had come to litigation in the SCO case. Whilst IBM might have protected Novell, it might not have done, and where would that leave the boys from Utah? So Microsoft found very fertile territory in the Novell board. People whose real background was proprietary code, networking and unix; people who understood lock-in and licences, and people who were desperate for both more cash and for peace of mind that they would not be under attack from Microsoft. But, most of all, they were a company board who were desperate to do better than the market leader in their space, Red Hat, and also do better than the very well funded upstart, Ubuntu.

Microsoft played, as always, several Aces from each sleeve. They agreed to provide a seal of approval for Novell Linux; they agreed to stop fuding it in public. They wouldn’t actually stop, of course – they’d keep those Aces for later, and let Novell’s lawyers argue it out for as long as they could afford to, Microsoft never needs to keep any promises it makes, it’s rich enough to avoid that, another Ace up its sleeve. But more importantly, they agreed to not attack Novell’s customers legally, whilst agreeing not to reach a similar agreement with any other linux distributor.

Well, after a few hearty meals, glasses of beer, wine and spirits, how could an offer like that look anything other than gold-plated? What more could a CEO want than to protect both his company, and his customers, from Microsoft’s attacks? It would be bound to improve his company’s standing in the Linux world, and on the stock-markets. At least, that’s what a CEO, fresh out of the proprietary world would think. A CEO with experience of the free software world would’ve seen all the landmines, pitfalls and caltrops scattered along this road, and would also have been far more aware of GPL3 and why it was being written – to protect his company and his customers from precisely this problem.

I suspect that the real winner from this debacle with be GPL3, as it will highlight the persistent danger which Microsoft poses to the free software world. Microsoft have certainly lost the server battle and the mobility battle and are in the process of losing the embedded battle and the console battles; they look like they will also lose the desktop battle, although it might take longer, but they are very very cash-rich, very powerful, and have far from abandoned the war.

I strongly recommend that anyone who’s written off GPL3 as unecessary reconsiders their position in the light of the Novell/Microsoft deal.”

Novell Wants Peaceful Coexistence While Others Suffer

Red Hat is still doing well, but we continue to discover that Novell’s move was not oblivious to patents threats that could/would ensue. Here is some of the latest.

Novell clarifies $40M payment to Microsoft as ‘peace of mind’

…regardless of what was said behind closed doors, as the deal was signed, in order for Red Hat’s customers to perceive Microsoft threat to sue Linux users as even partially credible, it needs the market to perceive Novell’s $40 million as respect for its patents. Period. Was the timing of Ballmer’s up-ratcheted rhetoric coincidental? You be the judge.

Retrieval statistics: 21 queries taking a total of 0.113 seconds • Please report low bandwidth using the feedback form
Original styles created by Ian Main (all acknowledgements) • PHP scripts and styles later modified by Roy Schestowitz • Help yourself to a GPL'd copy
|— Proudly powered by W o r d P r e s s — based on a heavily-hacked version 1.2.1 (Mingus) installation —|