madison

Linux needs a home Base

Evan Leibovitch | April 6, 2001 12:00 AM PDT

Summary

The Linux Standard Base group has been slow to produce a fullspecification, but it's worth the wait.
Twoweeks ago I outlined some of the impediments facing both open sourceand commercial software developers. The variety of companies and groupsthat distribute Linux-based operating systems has resulted in myriad filelocations, install formats, and other fields within the base operatingsystem. This extreme diversity has kept many developers away from Linux,and has caused others to waste time and resources making multiple versionsof applications or installation procedures.

To combat the problem, Linux Internationalcreated the Linux Standard Basegroup almost three years ago, with a mandate to develop a single platformspecification that developers could target and distributors couldimplement. The group has hit a number of bumps since then, including abrief (but loud) challenge from the renegade Linux StandardsAssociation in mid-1998 that lasted until the LSA faded away from lackof interest. And the LSB?s original plans to create a basic standard that simply dictatedrevision levels for common components were deemed unworkable.

Since then the LSB has been working on the tough and unsexy tasks ofdefining a standard, creating a sample implementation, and testing forcompliance. According to LSB organizers, the pace has picked upsignificantly over the last six months, sparked by additional resourcesfrom sponsors and by new members like George Kraft from IBM, who nowchairs the LSB's technical committee.

The group has already met a number of important milestones:

  • Release 1.1 of the LinuxDevelopment Platform Specification (LDPS) came out last month. It's apreliminary document designed to allow developers to write code that'seasily portable to all major Linux distributions.
  • The Linux InternationalizationInitiative is working towards global standards that can be used indistributions worldwide, regardless of regional differences.
  • Release 2.2 of the FilesystemHierarchy Standard (FHS) recently came out of beta. This important partof the LSB specifies what files go where. It's already being implementedin many distributions, including Caldera and SuSE, as a stepping stonetowards full LSB compliance.
  • Most importantly, there's a first shot at a reference implementationof an actual LSB-compliant system. It requires an add-onpackage that installs on top of the public beta ofCaldera's new distribution release. There's plenty more work to bedone, but it's a critical first step.
Another welcome addition has been the participation of The Open Group (TOG). Known as X/Openduring the Unix Wars, TOG became the custodian of the Unix trademark andis responsible for testing whether an operating system meets the criteriathat allow it to be called Unix. In an effort driven by TOG employeeAndrew Josey, the group now has provided the LSB with valuable test suites andother resources.

The Open Group's involvement is also good news for those who areinterested in bridging the gaps between Linux and Unix standards. WhileLinux likely will never conform to The Open Group's Unix specifications,cooperation at this level benefits those moving between the Unix and Linuxworlds.

So where exactly is the complete LSB specification at this time? Right nowit's at version 0.7.4 and moving ahead rapidly. "You will see a successfulLSB 1.0 in 2001 or I'll publicly eat my tennis shoe," Scott McNeil, LSBspokesman, told me.

That's good to hear, because the LSB really needs to have its spec outthis year. Waiting three years hasn't really been much of a problem. Afterall, it's taken that much time for Linux to reach an installed base (notto mention the technical maturity) capable of attracting conventionalcommercial developers. But as Linux moves further into the computingmainstream, the absence of a standard porting platform forces developersto take matters into their own hands, as I described in my previouscolumn.

I'd especially prefer not to have a situation in which applicationscompanies feel pressed into making their own Linux distributions,specially designed to run their software. This has already happened atleast once, in the form of the Japanese Miracle Linuxdistribution, designed expressly by and for Oracle.

Or, worst of all, developers will just shrug their shoulders at the wholeperception of Linux fragmentation and not develop for the platform atall.

It's critical for the LSB specification to produce a stable target forLinux developers, especially for vendors of proprietary packages thatwon't come with source code. While it's important that LSB adherence beoptional -- not every specialized distribution has the need to runproprietary applications -- the existence of a cross-vendor standard willbecome rapidly accepted throughout the community once it's out.

I know and like many people within the LSB. I like the path it has taken,and I think it has been correct to do it right rather than rush it. WouldI have preferred a full spec sooner? Of course--who wouldn't? But inreality, the long wait is acceptable given the pubescent stage of Linux'smaturity as a mainstream OS.

Still, there is a limit to patience, and in the absence of a standard,developers will either figure out their own or just stay away -- andneither of those options is pleasant. If the LSB doesn't deliver a fullspec this year we'll have more to worry about than the taste of ScottMcNeil's shoes.

Has the LSB taken too long? Tell Evan in the TalkBack below or in the ZDNet Linux Forum. Or write to Evandirectly at evan@starnix.com.

Talkback - Tell Us What You Think

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity