Linux Archive

The Linux Kernel version 2.6.25 introduces a new Linux process sleeping state, TASK_KILLABLE: If a process is sleeping killably in this new state, it works like TASK_UNINTERRUPTIBLE with the bonus that it can respond to fatal signals. This feature is generally an improvement over the existing options -- after all, it is another way to keep from getting stuck with dead processes.

Lennart Poettering, main programmer of the PulseAudio project, has written a 'Guide Through The Linux Sound API Jungle': "At the Audio MC at the Linux Plumbers Conference one thing became very clear: it is very difficult for programmers to figure out which audio API to use for which purpose and which API not to use when doing audio programming on Linux. So here's my try to guide you through this jungle."

I'm generally not very fond of reporting on security breaches or bugs, but OSNews reader and Mandriva employee Adam Williamson warned us of a pretty serious bug in pre-releases of the Linux kernel. "A major bug has been found in the e1000e module (which supports some Intel onboard ethernet adapters) in Linux kernel 2.6.27 pre-releases (up to and including 2.6.27rc7). It can cause the EEPROM of the adapter to become corrupted, rendering it non-functional. This may affect current pre-releases of distributions. Mandriva has posted a detailed notification about the issue, as has SUSE." So, watch out.

Greg KH, Linux kernel developer delivered a keynote in the Linux plumbing conference about the health of the ecosystem. His message was essentially that distributions that don't contribute to the ecosystem have to rely on the whims of others which is unhealthy for them. Here is an introduction the development model and some interesting statistics about the Linux kernel code. Update by TH: Rebuttals are appearing all over the web, like this one by Canonical's Matt Zimmerman ("He's refuting a claim which has, quite simply, never been made. When this sort of thing happens on mailing lists, it's called trolling."), or this one by another Canonical employee, Dustin Kirkland.

Ottawa Canada Linux Users Group recently hosted another of its Kernel Walkthrough tutorials given by Bart Trojanowski. The screencast starts with a one-hour presentation on the components involved, and then dives into the code which bootstraps the kernel on the 32bit x86 platform. The first Kernel Walkthrough by the Ottawa Canada Linux Users Group covered Linux development background, file layout and data types.

"Once upon a time, a Linux distribution would be installed with a /dev directory fully populated with device files. Most of them represented hardware which would never be present on the installed system, but they needed to be there just in case. Toward the end of this era, it was not uncommon to find systems with around 20,000 special files in /dev, and the number continued to grow. This scheme was unwieldy at best, and the growing number of hotpluggable devices (and devices in general) threatened to make the whole structure collapse under its own weight. Something, clearly, needed to be done." The solution came in the form of udev, and udev uses rules to determine how it should handle devices. This allows distributors to tweak how they want devices to be handled. "Or maybe not. Udev maintainer Kay Sievers has recently let it be known that he would like all distributors to be using the set of udev rules shipped with the program itself." ComputerWorld dives into the situation.

Linux project lead Linus Torvalds has said it is not easy to become a major contributor to the Linux kernel. In an email interview with ZDNet.com.au sister site ZDNet.co.uk last week, Torvalds said that, while it was relatively easy for coders and organisations to contribute small patches, the contribution of large patches, developed in isolation, could lead to both new and established contributors becoming frustrated. "The kernel is about pretty harsh technical issues, and mistakes are really frowned upon," wrote Torvalds. "In an OS kernel, there are simply more security and stability requirements, and the bar is really higher in some respects. That will inevitably also reflect in the response to patches."

InformationWeek is speculating on how Linux will change in the next four years. "By 2012 the OS will have matured into three basic usage models. Web-based apps rule, virtualization is a breeze, and command-line hacking for basic system configuration is a thing of the past."

As we all know by now, netbooks are the latest craze in the computing world. Small notebooks, perfect for on the go, and relatively cheap. The interesting thing is that these netbooks are often offered with Linux pre-installed instead of Windows, and this prompts many to believe that it is the netbook niche where Linux will gain its first solid foothold among the general populace. "It does a lot to level the playing field. In fact, Linux looks to be quick out of the gate," said Jay Lyman, analyst with the 451 Group. However - is that really happening?

ACM has announced the availability of the SIGOPS Operating Systems Review, an Issue on Research and Developments in the Linux Kernel. It is available, for free, from the ACM Archives site. The issue has 12 papers about the advances that have been merged or are candidates to be merged into the Linux kernel, as well as new idea papers discussing promising experimental work.

Not all Linux distributions are made with the same components, which can make it difficult for software developers to write applications for multiple Linux distributions. That's where the Linux Standards Base (LSB) comes into play. For years the LSB has not quite lived up to its full potential. That could all change with the upcoming LSB 4.0 release.

Take a look at the strategy of treating Linux instances as managed objects. Previous generations of management technologies all suffer from the problems of excessive complexity, heavyweight implementations, too fine-grained an approach, and so on. In effect, the area of Linux systems management infrastructure is wide open for a root and branch review.

SplashTop is an instant-on Linux environment created by DeviceVM. SplashTop does not intend to provide a full computing environment, but it satisfies a home user's basic needs such as email, VOIP, IM, etc. Asus is the primary partner of DeviceVM and SplashTop started to get bundled with Asus motherboards and Asus notebooks. Now the good folks over at the Phoronix Forums have hacked SplashTop to run from a USB stick on non-Asus motherboards, run custom applications and launch a terminal inside the Linux environment.

How does the system startup look like? This question usually does not come into mind of a normal computer user. Oh, he presses the power button, goes to the kitchen to make a coffee and when he comes back, the password can be entered on the screen in the prepared field. Sometimes however, in the minds of a bit more keen computer enthusiasts, the question is born "how does it actually work?" It's no black magic. Editor's Note: An in depth three part series about the computer boot up process was covered earlier in OSNews.