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

Intel Pentium vs. AMD Ryzen 3 Performance For Linux Gaming

For those that may be looking to assemble a new low-end Linux gaming system in early 2018, here is a look at the Linux gaming performance of an Intel Pentium (Kabylake) processor to an AMD Ryzen 3 while testing with the GeForce GTX 1050 and Radeon RX 560 graphics cards. Read more

Containers, the GPL, and copyleft: No reason for concern

Though open source is thoroughly mainstream, new software technologies and old technologies that get newly popularized sometimes inspire hand-wringing about open source licenses. Most often the concern is about the GNU General Public License (GPL), and specifically the scope of its copyleft requirement, which is often described (somewhat misleadingly) as the GPL’s derivative work issue. One imperfect way of framing the question is whether GPL-licensed code, when combined in some sense with proprietary code, forms a single modified work such that the proprietary code could be interpreted as being subject to the terms of the GPL. While we haven’t yet seen much of that concern directed to Linux containers, we expect more questions to be raised as adoption of containers continues to grow. But it’s fairly straightforward to show that containers do not raise new or concerning GPL scope issues. Read more

Get ready to use Linux containers

One of the most exciting things to happen in the Linux world in the past few years is the emergence of containers — self-contained Linux environments that live inside another OS and provide a way to package and isolate applications. They're not quite virtual systems, since they rely on the host OS to operate, nor are they simply applications. Dan Walsh from Red Hat has said that on Linux, "everything is a container," reminding me of the days when people claimed that everything on Unix was a file. But the vision has less to do with the guts of the OS and more to do with explaining how containers work and how they are different than virtual systems in some very interesting and important ways. Read more

Samsung unveils 860 PRO and EVO SATA SSDs with improved Linux compatibility

If you haven’t yet upgraded your operating system drive from a mechanical hard disk to a solid state drive, you are really missing out. Prices have dropped dramatically over the years, while at the same time, reliability has improved. Swapping an HDD for an SSD can be very easy too, thanks to cloning software that often comes with the drive. Before you buy some random SSD, please know that they are not all the same. True, SATA models largely have equal speeds these days, but the brand really matters from a reliability standpoint. If you want a dependable solid state drive for your data, you should take a look at Samsung. Its offerings are top notch, and today the company launches its newest SATA models -- the 860 PRO and EVO. Read more