Linux Standard Base
|
Jeff Licquia Software Developer The Linux Foundation |
- Submitted on Dec 23, 2008
I am pleased to announce the availability of LSB 4.0 Release Candidate 1.
This version of LSB 4.0 has been put in the normal release directories, but IS ONLY A RELEASE CANDIDATE! In particular, certification is not yet open for LSB 4.0.
We are continuing to use the previously-announced beta page for accessing information on LSB 4.0 prereleases. That page can be found at:
- Submitted on Sep 26, 2008
Last week, I attended the Linux Plumber's Conference, a funny-sounding but very important conference. My wife can't get the image of Mario and Luigi out of her head, but "plumbing" in this case concerns the flow of data between core parts of the Linux system, not the flow of water.
One of the important mini-conferences held there was the Audio Conference, run by Lennart Poettering. A good portion of the miniconf was spent discussing good end-developer APIs for sound on Linux, or (more accurately) the lack thereof. Lennart talked about his ideas, but was intentionally vague about many of them, promising to follow up later with some documentation.
- Submitted on Aug 25, 2008
Picking up where we left off last time…
The LSB spec invents things without consulting distros. Like the whole init scripts thing. But that’s not as bad as depending on RPM or requiring a specific layout.
- Submitted on Aug 18, 2008
So it looks like the project I’ve been laboring on has been getting some attention:
Ever thought it was difficult to write software for Linux? For multiple distros? InternetNews reports that the LSB is making a push for their next release (due out later this year) that should help make all that much easier.
- Submitted on Aug 7, 2008
Let’s take a trip down Memory Lane, shall we?
Back when we were still the Free Standards Group and OSDL, the FSG side of the house was hard at work on a developer portal that would help new Linux developers learn what they needed to write applications for Linux. We eventually did a release, but it didn’t have many of the features we wanted, and integration with the tools we provide in the LSB was spotty and hard to use. One thing led to another; the merger happened, and for a while, we were busy with lots of other important things, and the LDN fell by the wayside.

