Language Selection

English French German Italian Portuguese Spanish

Torvalds: How to Keep Linux Kernel on Course

Filed under
Linux

The rapid pace of Linux development appeared to hit a roadblock last year with the industry's decision to forestall development of the Linux 2.7 kernel. Linux vendors and developers wondered if tweaking a single, stable 2.6 kernel could work in practice.

According to open-source insiders, the move to create separate kernel trees for technology testing and bug fixes, which are then incorporated into the stable kernel when ready, has been a huge success, pleasing both kernel developers and the vendors who distribute the open-source operating system.

"I'm certainly pleased, and judging from the reactions we had at the Linux Kernel Summit in Ottawa a few weeks ago, most everybody else is too," Linus Torvalds, the founder of the Linux operating system, told eWEEK.

The biggest advantage of staying with 2.6.x was that developers do not have two different trees between which they need to port patches, which makes them happy, he said.

Linux vendors tend to like the move, because the upgrades are more gradual, rather than the huge, and potentially painful, jumps of the past.

This shift started at the 2004 Linux Kernel Summit with the decision to no longer have a separate kernel development tree, but to keep adding new features, technologies and patches to the existing 2.6 stable tree, Greg Kroah-Hartman, a Linux kernel developer with Novell, told attendees at the annual O'Reilly Open Source Convention last week.

That decision has spawned three separate 2.6 trees: The first is the mainline or stable kernel, known as 2.6.x and which is maintained by Torvalds; the second is known as the 2.6-mm tree, and is where technologies are tested before they get into the mainline kernel; and the third is the 2.6.x.y kernel (known as the .y kernel), which is for bug fixes only.

The .y kernel is governed by a set of strict rules, including that the fix has to be less than 100 lines, that it applies to something already in the mainline kernel, and there had to be a three-day public review of all patches to allow all involved parties time to express their view and to make sure that everyone bought in, Kroah-Hartman said.

There were 12 2.6.11.y releases, with just 507 lines added and 303 lines removed, "which is the way to just get things fixed and I think shows that this process is working. These fixes also go into the mainline release and the 2.6.11.y was dropped when the 2.6.12 release came out. There have been four 2.6.12.y releases so far, with the latest released last Friday," he said.

The 2.6.12.y releases have had just 169 lines added and 199 lines removed.

"We are not back porting big experimental things into the .y-series," he said.

But there needed to be a mechanism for testing new technologies, a place where they could be revised, updated and even removed before actually getting into the mainline kernel.

Full Article.

More in Tux Machines

Linux Kernel 3.19-Rc6 Released


Linux Kernel 3.19-Rc6 Released

One more rc released today shortening time period for the final release. Each release sees a new changes and fixes and this one is slightly smaller but as always better.
 
 
 
 
 
 

Read at LinuxAndUbuntu

Ubuntu Flavors 15.04 Vivid Vervet Alpha 2 Released


Picture

Ubuntu flavors 15.04 alpha 2 has been released for testing. Ubuntu Unity does not take part in the alpha releases. Flavors like Kylin, Ubuntu Gnome, Lubuntu and Kubuntu alpha 2 relases are available.



Read at LinuxAndUbuntu

MBARI testing the waters with open source camera

“There is a movement to have open source oceanographic equipment,” said Chad Kecy, lead designer and MBARI engineer. “Anyone could take our designs and modify them for specific needs they have. It’s just a less expensive and easier way of getting cameras in the water.” Read more

Fixing unperceived errors in my X Windows configuration

Last week I decided to bite the bullet and upgrade X Windows to the latest version available in the main Portage tree. After rebooting, X Windows, GLX and Direct Rendering worked fine as usual. So everything was good. Well, not quite. Although the installation was working properly, there were still some long-standing messages in the X.Org log file that indicated my installation was not configured completely correctly. I had ignored them for too long and resolved to find their causes and eliminate them. Here is what I did.

Read more