Practical Technology

for practical people.

February 15, 2007
by sjvn01
0 comments

Yes, there is a PJ

According to Forbes, SCO recently tried to subpoena Pamela “PJ” Jones, editor of the popular Groklaw legal news website. They were not successful. I’ve been unable to confirm with SCO that they indeed attempted to have Jones file a deposition for one of their Linux-related lawsuits. Since this incident was reported to have happened, Ms. Jones announced on Groklaw that she has “been sick more than once recently. I don’t seem to be getting back on my feet the way I’d normally expect, and so after some thought I’ve decided to take a little break from doing Groklaw, just until I get my strength back.”

Since then, Groklaw has been kept updated by the site’s webmaster, Peter Roozemaal, aka MathFox. Jones, herself, has been quiet.

As a result of all this, there are once more rumors flying about that “Pamela Jones” is not a real person. Or, as SCO CEO Darl McBride once put it, Jones is a front for anti-SCO parties, such as IBM, and she’s not who she says she is — a paralegal who’s also a journalist.

Let me address this directly. Yes, Pamela Jones is a real person. I’ve met her several times, and I’ve often “talked” with her on email and IM. I consider her a friend.

She is not a front for anyone. She is a paralegal, hence her excellent legal research skills, which are the foundation of her stories. And, she’s a journalist by any standard I know of.

What I find surprising, frankly, is that Jones has been able to keep up her production at as high a level as she has over the years. She has been driven by her passion for open source and fairness to produce a remarkable body of work.

Let me add that while I can sing her praises, we don’t always agree. I take it a far kinder view, for example, of Novell’s relationship with Microsoft than she does.

I also have an entirely different slant toward the public knowing about me. If you want to know more about me, it’s pretty darn easy to find out anything you might want to know. Jones, however is a highly private — even shy — person in her personal life.

She also was hoping that by being semi-anonymous “people could assume whatever they wanted and just focus on what I said, rather than on who was saying it. For that reason, I chose PJ, because it could be anyone, either sex, any nationality, anyone and no one in particular.”

Regardless of PJ’s exact identity — no, she’s never shown me her passport — here’s what’s really important. Jones has made her reputation as a top legal IT reporter from her work detailing the defects with SCO’s case against IBM and Linux. Indeed, it is no exaggeration to say that her work has contributed enormously to everyone’s coverage of SCO’s cases.

Speaking as a writer who can argue that he’s covered The SCO Group, and its predecessor companies Caldera and The Santa Cruz Operation, more closely than anyone else, save one, in journalism over the years, I have to take my hat off to Pamela Jones. I’ve written hundreds of stories about SCO; she’s written thousands.

Groklaw, as the SCO lawsuits wind their way to what appears to their final ending, under Jones’s direction, has also been expanding its legal IT coverage to DRM (Digital Rights Management), Microsoft’s legal battles, and open document standards.

The SCO cases will go away. SCO may go away. But, once Jones has her health back, Groklaw will continue.

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

February 12, 2007
by sjvn01
0 comments

Microsoft, Novell expand on technical collaboration plans

Microsoft and Novell on Feb. 12 unveiled more specifics regarding their joint technical roadmap. As expected, the two companies are collaborating on four areas of technology that address significant problems faced by enterprises: virtualization, Web services for managing physical and virtual servers, directory and identity interoperability, and document format compatibility.

In virtualization, Microsoft and Novell are jointly developing a virtualization offering for Linux and Windows Server to consolidate server workloads in heterogeneous data centers. When the project is completed, users will be able to run SLES 10 (SUSE Linux Enterprise Server) as a virtualized guest on an upcoming “service pack 1” update to Microsoft Virtual Server 2005 R2.

In addition, in the next version of Windows Server, codename Longhorn, SLES 10 will run as an enlightened guest using its built-in Longhorn’s virtualization technology. On the Linux side, Longhorn will run as a paravirtualized guest on SLES 10 using Xen virtualization technology.

All these new virtualization mechanisms are expected to arrive in 2007, according to the companies. Virtualization is the first goal for the recently announced Novell and Microsoft joint labs.

The unlikely operating system pair is also working on the foundation for joint Web services-based management tools for Linux and Windows Server. This collaboration on standards-based solutions for managing heterogeneous environments should make it easier for companies to manage their mixed Windows and SUSE Linux Enterprise physical and virtual environments.

The Web Services for Management (WS-management) specification supports the DMTF (Distributed Management Task Force) initiative to expose model-agnostic management resources via a set of Web services protocols. At the same time, Novell is working with the open source community to develop an open-source implementation of the WS-Management specification. Novell ZENworks Orchestrator and Microsoft System Center Operations Manager 2007 is expected to incorporate WS-Management this year, the companies said.

WS-Management is a vendor-neutral core set of Web service specifications that’s meant to define the common set of operations that all systems management systems must use. WS-Management’s goal is to support interoperability between management applications and managed resources. In addition to Novell and Microsoft, Sun, Intel, and Symantec, among many others, support WS-Management.

Microsoft and Novell are working toward improving directory and identity interoperability between Novell eDirectory and Microsoft AD (Active Directory). The WS-Management tools will work with both AD and eDirectory to produce improved IT resource access control for network administrators, the companies said.

Microsoft and Novell are also continuing their work delivering seamless interoperability between office productivity applications. This is primarily being done through the joint open source project to create a bi-directional translator for documents, spreadsheets and presentations between OpenOffice.org’s ODF (OpenDocument format), and Microsoft’s Open XML.

The first version of the ODF/Open XML translator arrived on Feb. 2. This version of the Open XML/ODF Translator supports Microsoft’s Office 2007, Office 2003, and Office XP. Additionally, later this month, Novell will release an Open XML/ODF Translator for the Novell edition of OpenOffice.org.

Microsoft and Novell will also be developing a series of interoperability demonstrations that focus on interoperability between technologies and products from both companies. A more detailed roadmap for this collaborative effort will be available in the first half of 2007.

Jeff Jaffe, executive vice president and CTO at Novell, stated, “The majority of our customers have mixed-source environments, and they want their platform vendors to take responsibility for making things work together. That’s what our technical collaboration agreement with Microsoft is all about. We’re working together to deliver true interoperability between Windows and SUSE Linux Enterprise, and we are standing together behind our products and our customers.”

Bob Muglia, Microsoft’s senior VP of the Servers and Tools Business, added, “We’re working on reducing costs and improving flexibility in the data center so customers can focus on managing their businesses, not their IT systems.”

Al Gillen, research VP for system software at IDC, stated, “With this first installment of the Microsoft-Novell development roadmap, we see that both companies are building on this relationship to develop real, product-specific solutions to deliver on the promises made to customers. The great potential of the November announcement between Microsoft and Novell could have been disappointing without a product-specific roadmap to execute against. With the roadmap, the technology benefits customers can expect will be tangible and delivered on a predictable basis.”

A version of this story first appeared in Linux-Watch.

February 12, 2007
by sjvn01
0 comments

Intel, Novell deliver virtual Windows drivers to Linux

Although Microsoft and Novell are collaborating on virtualization to enable Windows Server to run on SUSE Linux, and vice-versa, Novell and Intel have advanced toward that goal with the release of paravirtualized network and block device drivers that allow Windows Server to run unmodified in Xen virtual environments.

These device drivers support SUSE Linux Enterprise Server 10 (SLES), and work on Intel-based server platforms featuring chipsets using Intel-VT (Virtualization Technology). The new drivers will let customers migrate to newer and fewer energy-efficient servers, consolidating legacy Windows or Linux solutions onto virtual servers.

The two companies have been working on Xen VT drivers since this summer. The first release of a VT driver for SLES was in September.

The new Linux kernel, 2.6.20, also supports Intel-VT and AMD-V (aka Pacifica) virtualization technology. Instead of Xen, however, the new kernel comes with the newer KVM (Kernel-based virtual machine for Linux).

In addition to providing cost savings when virtualizing Windows on SLES, Novell and Intel claim that these new drivers can improve the availability of Windows- and Linux-based workloads via clustered virtual systems, and help IT staff respond faster to business needs by easily creating and provisioning services on virtual systems.

“With our SUSE Linux Enterprise 10 platform launch in July 2006, Novell became the first major Linux distributor to integrate Xen virtualization into a Linux distribution,” said Jeff Jaffe, Novell executive VP and CTO in a statement. “In September, we became the first distribution to support virtualized Linux workloads on Xen, and today we are the first distributor to support virtualized Windows workloads on Linux.”

“Intel has been working with the open source community to enable Linux virtualization solutions to take advantage of Intel Virtualization Technology, so that guest OS and applications can run unmodified,” added Doug Fisher, Intel’s VP of software and solutions group.

“In addition, our Quad-Core Intel Xeon Processor-based platform with its outstanding performance, energy efficiency and reliability provides unparalleled headroom for multiple Virtual Machines running varied data center workloads,” Fisher added. “Getting Windows to run with Linux unmodified and vice versa will bring an immense confidence boost to IT managers in making decisions on corporate platform standardization and refresh.”

Novell is sponsoring a virtualization pilot program for customers, providing enterprise-level support for running fully virtualized Windows 2000/2003/XP workloads on SLES. The paravirtualized device drivers are now available to members of the pilot program. General availability is scheduled for later this year.

For more information on the pilot program and Novell virtualization solutions, visit Novell’s virtualization site. For more details about Intel-VT, visit Intel’s VT site.

A version of this story first appeared in Linux-Watch.

February 10, 2007
by sjvn01
0 comments

Vista’s Multimedia Mess

Now, as those of you who follow my adventures in such sites as Linux-Watch and DesktopLinux know, I’m no fan of Windows in general. That said, I actually have had some success with Windows Media Center 2003 and 2005. As a result, I’ve used this operating system both to watch video on my PC and to my Sony HDTV via first a D-Link MediaLounge DSM-320 Wireless Media Player and now a D-Link DSM-520 MediaLounge Wireless HD Media Player Since then, I’ve also used Windows Media Player 11 for XP with good results.

So, when I started doing some serious testing work with Vista Ultimate, I assumed it work at least as well. I was so wrong.

Continue Reading →

February 8, 2007
by sjvn01
0 comments

Linspire, Canonical, Freespire, Ubuntu join forces

Canonical Ltd., the sponsor of Ubuntu, and Linspire Inc., the developer of Linspire and Freespire, on February 8 announced a technology partnership to integrate with each other’s Linux distributions. Linspire/Freespire will be based on Ubuntu, rather than Debian, and Ubuntu will integrate with Linspire’s CNR package installer/updater.

Starting with Ubuntu’s 7.04 release in April, Ubuntu users will gain access to Linspire’s newly opened CNR (Click and Run) e-commerce and software delivery system. For Linspire, that will mean moving from Debian to Ubuntu as the base for its Linspire and Freespire desktop operating systems.

Continue Reading →

February 7, 2007
by sjvn01
0 comments

Linux hackers tackle WiFi hassles

When it comes to troublesome Linux peripherals, WiFi takes the cake. Sparked by the Portland Project’s efforts to bring standardization to the Linux desktop, the Linux wireless developer community tackled this problem at its second Linux Wireless Summit last month in London.

The Summit was scheduled as a followup to the January IEEE 802 standards committee meeting, which, among other issues, moved a step closer to making 802.11n a real IEEE standard. As a result of this timing, participants at the Linux WiFi meeting included kernel developers and vendor representatives from Intel, Broadcom, Devicescape, MontaVista, and Nokia.

Once there, according to Stephen Hemminger, Linux Wireless Summit co-coordinator and a Linux software developer at the Linux Foundation, the attendees had a very productive meeting.

Still, it’s been slow going in some critical areas of Linux and WiFi, according to John Linville, the Linux wireless software maintainer. In particular, Linville reported that development work is proceeding too slowly on a new 802.11 stack (d80211); and with a new WiFi API (cfg80211), “development is even slower.” Hemminger described the cfg80211 as “a good start but there are no user interface tools (the iproute2 equivalent of iwconfig).”

As for d80211, a breakout session addressed its technical issues. Hemminger wrote in his report on the summit that most of its problems “are not specific to the d80211 stack but have existed all along in Linux wireless. The problem is that up to now each device was doing its own different implementation. The d80211 stack currently exposes a ‘master’ interface which is only used for reconfiguring the internal queuing disciplines. Since the master interface shows up as a device, it can be a potential point of bugs or user confusion so there was discussion on ways to get rid of it prior to acceptance in the main kernel.”

There was also a discussion of the d80211 stack’s more advanced features that are seeing little use as of yet. In particular, Nokia was interested in QoS (Quality of Service) and WMM (WiFi Multimedia) support, because their existing device uses a proprietary userspace library.

As it is, “D80211 supports WMM based on the IP type of service (TOS) value in the socket API,” Hemminger added. This led to a discussion of whether or not existing glibc header files include the right values for WMM/TOS. It was noted that many existing multimedia applications, like Ekiga, Skype, and Google Talk, are not properly setting TOS.

Another breakout session dealt with regulatory concerns. This discussion led the group into facing the dilemma of proprietary hardware and firmware. According to Hemminger, “Hardware vendors license their equipment under FCC section 15 regulations, even though technically pure software devices could be under SDR (Software Defined Radio) regulations. FCC wants all devices to have a ‘no trespassing’ sign on radio settings but there is no consensus on what that means.”

As a result, “the only solution that can get certified in the current regulatory environment is to have a closed source component either in firmware (good), kernel (bad) or userspace (less evil),” Hemminger continued. The reverse-engineered drivers don’t have this problem, but the developers were concerned about the legal implications of redistributing them. “There is some concern since FCC has already stopped hackers who modify power levels on access points. Vendors are reluctant to address the SDR issues too directly because of the regulatory impact to existing non-Linux products if there was any problem.”

The reason why the FCC takes this position is that the governmental agency doesn’t want it to be easy for users to tamper with radio settings or power levels. Thus, the only WiFi solution that can be certified must have a closed source component. Thus, as distasteful as it is to some free software distributors, legal support for WiFi on Linux will often have to incorporate proprietary elements in one way or another.

Coming out of the meeting, the developers committed to make experimental wireless tarball (and driver) packages available; move faster on the new cfg80211 API; and gain a more complete understanding of the regulatory WiFi situation.

The next Linux Wireless Summit will be this fall, most likely in October, on either the U.S. East Coast or in Israel.

A version of this story first appeared in DesktopLinux.