Commentary

Serdar Yegulalp
 

Linux Standards Base 4: Herding Cats?

Is any attempt to standardize Linux akin to herding cats, especially given the proliferation of distributions and packages? Jim Zemlin doesn't think so, and has been trying to do something about it via the Linux Standards Base.

Is any attempt to standardize Linux akin to herding cats, especially given the proliferation of distributions and packages? Jim Zemlin doesn't think so, and has been trying to do something about it via the Linux Standards Base.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I talked with Jim Zemlin about the LSB back at the Red Hat Summit, and according to his description of it, the incarnation they had at the time was mainly intended to insure that server applications had a stable platform to build on. Desktop apps weren't part of the picture, but after reading a piece in InternetNews about the LSB, I realize that was just a question of scope for that iteration of the LSB.

The newest version of the LSB, set to be finalized by November of this year or so, is about stabilizing the APIs that are used in the major distributions (Red Hat, SUSE, Ubuntu), and so on. Many of the things in the version 4 road map have been badly in need of some kind of overall plan: high-level frameworks for multimedia, for instance. (ALSA, GStreamer and PulseAudio are specifically mentioned in the 4.0 map.) This part I'm especially curious about, since it represents one of the areas where Linux still has a lot of progress to make, apart from the efforts of individual projects.

One key component of the LSB is a test suite that anyone can use to determine if a given application they've put together is LSB-compliant. There's no way to guarantee that someone else will hew to the LSB, but Jim's idea is that anyone who cares about having their application run seamlessly on most editions of Linux, will take the effort to run the test suite. And by making the bar for compliance as low as possible, there'll be little reason not to. In short, not complying with the LSB will be its own punishment.

Is that the most effective way to do it? In the Linux world, it might well be -- but the real proof will be to see how much adherence there is to the 4.0 standard a year or more after it's been published. I'm also wondering whether the more maverick distributions will even think of this as something to hew to, or to dissent from. After all, if Linux's big defining trait is its diversity, will that include diverging from things that are meant to give the community that much more solidarity?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links