Practical Technology

for practical people.

July 2, 2007
by sjvn01
0 comments

Microsoft, Newspeak and Open XML

One of the most chilling concepts of George Orwells novel “1984” is “Newspeak.” In Newspeak, the language is constantly being cropped of words that might lead to “thoughtcrimes.” If you control the language, the logic goes, you control what people think.

Microsoft is doing exactly this with its “Open XML.” Its meant to remind you of open source—a term which is now fighting to maintain its integrity—and, in particular, of open standards.

Open standards, most of us in the IT business agree, are good things. If we didnt have open standards, wed still be stuck with half-a-dozen incompatible versions of the C programming language, we wouldnt have universal 802.11g Wi-Fi, and so on. Of course, reaching though standards can be a long, painful experience, as anyone who has followed the 802.11n Wi-Fi standard wars knows.

Microsoft, however, isnt really trying to win the open-standard wars in document formats between its own Open XML and the truly open ODF (Open Document Format). Instead, its appearing to be willing to compromise and to make it easy to translate from the two formats.

In fact, its even working with rivals like Novell and Xandros to make it easier to translate from the two formats.

Sounds good, doesnt it?

Microsoft is winning, as we can see from Massachusetts decision to support Microsofts Office Open XML format in addition to ODF. Massachusetts, in case youve forgotten, is where the open document format war started. Massachusetts CIO at the time, Peter Quinn, said “Government is creating history at a rapidly increasing rate, and all documents we save must be accessible to everybody, without having to use closed software to open them now and in the future.”

Great idea, but from the reaction from some Microsoft lobbyists you would have thought hed proposed throwing babies to packs of starving dogs.

When it became clear that Microsoft couldnt just bulldoze open document standards away, the company decided that it should open up Office 2007s document formats. At the time, Id said Microsoft would find a way to poison its open standards. I was right.

Standards expert and attorney Andy Updegrove explains the current open standard trap well in his Standards Blog. Where does this leave proponents of ODF now? Clearly, if Ecma 376 (the official standard that hides Open XML) achieves equal status with ODF in Massachusetts, it will be a cause of great disappointment.

One can assume that privately, if not publicly, ODF opponents will have a field day one-on-one with other government purchasers, and will declare the open format battle over. Indeed, earlier in 2007 Microsoft did just that, calling a unilateral truce and announcing that there had been “two winners”

Updegrove continued, “After all, two years ago Microsofts formats were closed, and now they have been adopted by Ecma, and perhaps may soon be adopted by ISO/IEC as well. Bringing Microsoft to this point is, from that perspective, a victory indeed.

“But this would likely be a Pyrrhic victory at best. Office still commands a huge lead in the marketplace, and its ability to outspend the new entrants (many open source) into the office productivity suite marketplace will be enormous. If no one is buying ODF-compliant products, no one will develop them. And if no one is developing them, no one will be competing with Microsoft.

“And if no one is competing with Microsoft, then no one will care whether Microsoft contributes new features to Ecma or maintains them as proprietary extensions of Ecma 376, or whether it fully implements Ecma 376, or whether, in fact, it continues to support Ecma 376 at all. And then we will be right back where we started—dependent upon a single vendor, and with the accessibility of its all current documents, and indeed the history of our civilization, at risk.”

Why is Updegrove so full of doom and gloom? Isnt Open XML a standard? Arent there Open XML translators?

Hes down because hes tasted the poison in Microsofts so called open standard. Updegrove took a long, hard look at another Microsoft open-standard proposal before Ecma, TC46 – XPS (XML Paper Specification). This one, in case you dont know, is Microsofts latest attempt to stop Adobes PDF in its tracks.

“Why does this latest submission matter?” Updegrove asks. It matters because “it indicates a desire by Microsoft to institutionalize and expand a perpetual, standardized environment that would surround a single vendors products.”

The poison pill in both this and in Open XML is that Microsoft, not a standards organization, not a consortium of companies, gets to decide what goes into Open XML and what doesnt.

Sure, Open XML, all 4,000 or so pages of it, is sort of open now, but once ODF is off the table as a viable format, is it going to stay that way? Especially when it would be so easy to add just a bit of incompatibility here and there within such a monstrously sized standard?

Congratulations, Microsoft, it looks to me like youve played the Newspeak game very well and enough people are buying your “Open XML” is truly an open standard that we may be stuck with it. And that ensures that everyone will need to keep buying your Office programs instead of any of the others.

Life will be good for Microsoft stock holders. Lousy for every one else, but, come on, Microsoft doesnt believe in competition, it believes in winning by crushing its enemies, and making nice with customers only until Microsofts products are left as their only choice.

Best of all, thanks to your Newspeak, some fools already believe that Microsoft makes not only the best, but the most open programs. Excuse me. I feel a bit ill now.

A version of this story was first published in eWEEK.

June 22, 2007
by sjvn01
0 comments

Airport 2007: The Horror, the Humanity

Tight airline budgets and antiquated IT systems are making summer air travel more arduous than ever.

My summer travel horror show started on my way back from San Francisco after covering the inaugural Linux Foundation’s Collaboration Summit. About half an hour before the US Air flight to Charlotte, N.C. was to board, we were told there would be a 4-hour delay.

Not good. That delay ensured that there would be no way I’d make my local connection to my home in Asheville, N.C. Still, this kind of crap happens in today’s deregulated airline world. There is no slack left for travelers in any airline’s schedule. One delay quickly cascades into another, and you darn well better have a toothbrush in your carry-on bag.

Read More

June 18, 2007
by sjvn01
0 comments

Novell readies “virtual machine driver pack”

Novell Inc. claims it will become the first vendor to offer a supported solution for Xen virtual machine guests, with its release next month of the SUSE Linux Enterprise Virtual Machine Driver Pack.

This is a bundle of Xen-compatible paravirtualized network, bus, and block device drivers said to enable unmodified Windows and Linux guest operating systems to run on SLES (SUSE Linux Enterprise Server) 10 SP1 and Xen 3.0.4 with near-native performance in virtual environments on systems with Intel Virtualization Technology (Intel VT) and AMD Virtualization (AMD-V) chipsets.

It does this by opening additional channels of communication between the Xen hypervisor in SUSE Linux Enterprise and the unmodified guest operating systems running in a virtual environment, accelerating network and storage input/output and improving overall efficiency.

In recent months, virtualization has become hot in Linux circles. Besides advancements in Xen, the Linux kernel, as of version 2.6.20, includes its own built-in virtualization, KVM (kernel-basd virtual machine).

Some of this improved virtualization technology is now available for both the desktop, SLED (SUSE Linux Enterprise Desktop), as well as the server, SLES. Novell’s Xen can run unmodified Windows Server 2003 R2, Windows Server 2000, Windows XP, Vista, and Red Hat Enterprise Linux 4/5 as clients, according to Novell. VMware virtualization products are also supported on SLED, both as host and as guest, including VMware Workstation, Server, and Player.

The Driver Pack contains paravirtualized network, bus, and block device drivers for Windows Server 2003 (32 bit and 64 bit), Windows 2000 (32 bit) and Windows XP (32 bit and 64 bit).

Paravirtualized drivers for SLES 9 SP3 will be available later in 2007, Novell said. Similar device drivers for Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 will are expected to be available in the second half of 2007. Both the Red Hat and Novell drivers will be delivered as free updates to the Virtual Machine Driver Pack via Novell Customer Center.

The paravirtualized drivers for Windows in the Driver Pack are currently distributed under a proprietary license. The paravirtualized drivers for SUSE Linux and Red Hat Enterprise Linux, on the other hand, will be distributed under an open-source license.

The Virtual Machine Driver Pack will ship in July, according to Novell. A one-year subscription will be priced at $299 per physical server for up to four virtual machines, or $699 per physical server for unlimited virtual machines. Xen drivers for SUSE Linux Enterprise Server are already available and ship as part of the SUSE Linux Enterprise distribution.

A version of this story was first published in Linux-Watch

June 13, 2007
by sjvn01
0 comments

Forget about Linux going GPLv3

MOUNTAIN VIEW, CALIF. — If anyone out there still thinks that the main Linux kernel might change to the GNU GPLv3 (GNU General Public License Version 3) anytime soon, you can forget about it.

At the Linux Foundation Collaboration Summit at the Googleplex, five of the leading Linux kernel developers said that they couldn’t see anything like a good enough reason to switch to the forthcoming free software license.

Like Linus Torvalds, Linux’s founder and guiding light, the developers still dislike the GPLv3. During a panel on kernel development, when asked about the new GPLv3, due out on June 29, Greg Kroah-Hartman said that he had not changed his opinion that he thinks the “GPLv3 is bad.”

To justify switching Linux to the GPLv3 it “would have to be significantly better, and it’s not, said Kroah-Hartman. Ted T’so added that, “pragmatically speaking, it’s too much trouble for not enough advantage.”

Continue Reading →

June 13, 2007
by sjvn01
0 comments

Linspire, Microsoft in Linux-related deal

Linspire Inc. on June 13 announced an agreement to license voice-enabled instant messaging, Windows Media 10 CODECs, and TrueType font technologies from Microsoft for its Linux distribution. Additionally, Microsoft will offer protection to Linspire customers against possible violations of Microsoft patents by Linux, Linspire said.

In his June 14 weekly Linspire Letter, Linspire CEO Kevin Carmony stated, “This agreement will offer several advantages to Linspire Linux users not found anywhere else, such as Windows Media 10 support, genuine Microsoft TrueType fonts, Microsoft patent coverage, improved interoperability with Microsoft Windows computers, and so on.”

Linspire has long made an effort to bundle proprietary CODECs, drivers, and software with its Linspire and Freespire Linux distributions, as a way to offer users a Linux OS that works with a wide range of popular multimedia formats and browser plug-ins, and can play DVDs out of the box.

Continue Reading →

June 12, 2007
by sjvn01
0 comments

Linux founder still sees no reason to use GPLv3

The good news for GNU GPLv3 (General Public License version 3) supporters is that Linus Torvalds, the father of Linux, thinks the final draft is better than the earlier ones. The bad news is that he has “yet to see any actual reasons for licensing under the GPLv3.”

In a discussion on the LKML (Linux Kernel Mailing List) over the possibility of using both GPLv2, the open-source license now used by Linux, and GPLv3, which is scheduled to be finalized on June 29, Torvalds weighed in saying, “I consider dual-licensing unlikely (and technically quite hard), but at least _possible_ in theory.”

While Torvalds said he was “impressed [by the latest GPLv3 draft] in the sense that it was a hell of a lot better than the disaster that were the earlier drafts,” that doesn’t mean he actually likes it. “I still think GPLv2 is simply the better license,” Torvalds continued.

Besides, he dismisses most of the arguments for the GPLv3. “All I’ve heard are shrill voices about “tivoization” (which I expressly think is ok) and panicked worries about Novell-MS (which seems way overblown, and quite frankly, the argument seems to not so much be about the Novell deal, as about an excuse to push the GPLv3).” In “Tivoization” a device-maker uses GPLv2 code, such as Linux, but doesn’t release sufficient details of the system to enable users to install modified source code on the device (for example, signature keys required for modified binaries to run), under the argument that the appliance’s software was never meant to be user accessible.

In a latter message though, Torvalds concedes that there is at least one thing that might make him consider recommending Linux’s copyright owners to change to the GPLv3. “If Sun really _is_ going to release OpenSolaris under GPLv3, that _may_ be a good reason. I don’t think the GPLv3 is as good a license as v2, but on the other hand, I’m pragmatic, and if we can avoid having two kernels with two different licenses and the friction that causes, I at least see the _reason_ for GPLv3. As it is, I don’t really see a reason at all.”

Sun has gone back and forth on its commitment to place OpenSolaris under the GPLv3. After the news first broke that Sun was planning on dual-licensing OpenSolaris under the GPLv3 and its existing CDDL (Common Development and Distribution License), Richard Green, Sun’s executive VP of software, denied that Sun had made any such hard plans.

Torvalds also doubts that Sun will place OpenSolaris under the GPLv3 but, “hey, I didn’t really expect them to open-source Java either, so it’s not like I’m infallible in my predictions.”

Torvalds isn’t the only Linux leader who sees little chance of the bulk of Linux code moving to the GPLv3. Andrew Morton, the lead maintainer of the Linux 2.6 kernel, said, “I have yet to see Linus make a statement on these matters with which I didn’t agree.”

With little, if any, real support inside the core group of Linux developers, it seems very unlikely that Linux will become covered by the GPLv3.

A version of this story first appeared in Linux-Watch