Linux kernel

From Wikipedia, the free encyclopedia
  (Redirected from Linux Kernel)
Jump to: navigation, search
Linux
Tux
Tux the penguin, mascot of Linux[1]
Linux 3.0.0 boot.png
Linux kernel 3.0.0 booting
Company / developer Linus Torvalds and thousands of collaborators
Written in C, assembly[2]
OS family Unix-like
Initial release 0.01 (17 September 1991; 22 years ago (1991-09-17))
Latest release 3.15.6 (17 July 2014; 6 days ago (2014-07-17)) [±][3]
Available in English
Kernel type Monolithic
License GPL v2[4][5] plus various closed source binary blobs[6][7]
Official website kernel.org

The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions.[8] The Linux kernel is a prominent example of free and open source software.[9]

The Linux kernel is released under the GNU General Public License version 2 (GPLv2)[5] (plus some firmware images with various non-free licenses[7]), and is developed by contributors worldwide. Day-to-day development discussions take place on the Linux kernel mailing list.

The Linux kernel was initially conceived and created in 1991 by Finnish computer science student Linus Torvalds.[10] Linux rapidly accumulated developers and users who adapted code from other free software projects for use with the new operating system.[11] The Linux kernel has received contributions from thousands of programmers.[12]

History[edit]

In April 1991, Linus Torvalds, a 21-year-old student at the University of Helsinki, Finland started working on some simple ideas for an operating system. He started with a task switcher in Intel 80386 assembly language and a terminal driver. On 25 August 1991, Torvalds posted the following to comp.os.minix, a newsgroup on Usenet:

I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since April, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).

I've currently ported bash(1.08) and gcc(1.40), and things seem to work. This implies that I'll get something practical within a few months [...] Yes - it's free of any minix code, and it has a multi-threaded fs. It is NOT portable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(.

[...] It's mostly in C, but most people wouldn't call what I write C. It uses every conceivable feature of the 386 I could find, as it was also a project to teach me about the 386. As already mentioned, it uses a MMU, for both paging (not to disk yet) and segmentation. It's the segmentation that makes it REALLY 386 dependent (every task has a 64Mb segment for code & data - max 64 tasks in 4Gb. Anybody who needs more than 64Mb/task - tough cookies). [...] Some of my "C"-files (specifically mm.c) are almost as much assembler as C. [...] Unlike minix, I also happen to LIKE interrupts, so interrupts are handled without trying to hide the reason behind them.[13]

After that, many people contributed code to the project. Early on, the MINIX community contributed code and ideas to the Linux kernel. At the time, the GNU Project had created many of the components required for a free operating system, but its own kernel, GNU Hurd, was incomplete and unavailable. The BSD operating system had not yet freed itself from legal encumbrances. Despite the limited functionality of the early versions, Linux rapidly accumulated developers and users.

By September 1991, Linux version 0.01 was released on the FTP server (ftp.funet.fi) of the Finnish University and Research Network (FUNET). It had 10,239 lines of code. In October 1991, Linux version 0.02 was released.[14]

In December 1991, Linux 0.11 was released. This version was the first to be self-hosted - Linux 0.11 could be compiled by a computer running Linux 0.11. When he released version 0.12 in February 1992, Torvalds adopted the GNU General Public License (GPL) over his previous self-drafted license, which had not permitted commercial redistribution.[15]

A newsgroup known as alt.os.linux was started, and on 19 January 1992, the first post to alt.os.linux was made.[16] On 31 March 1992, alt.os.linux became comp.os.linux.[17]

The X Window System was soon ported to Linux. In March 1992, Linux version 0.95 was the first to be capable of running X. This large version number jump (from 0.1x to 0.9x) was due to a feeling that a version 1.0 with no major missing pieces was imminent. However, this proved to be somewhat overoptimistic, and from 1993 to early 1994, 15 development versions of version 0.99 appeared.

On 14 March 1994, Linux 1.0.0 was released, with 176,250 lines of code. In March 1995, Linux 1.2.0 was released (310,950 lines of code).

Version 2 of Linux, released on 9 June 1996, was followed by additional major versions under the version 2 header:

  • 25 January 1999 - Linux 2.2.0 was released (1,800,847 lines of code).
  • 18 December 1999 - IBM mainframe patches for 2.2.13 were published, allowing Linux to be used on enterprise-class machines.
  • 4 January 2001 - Linux 2.4.0 was released (3,377,902 lines of code).
  • 17 December 2003 - Linux 2.6.0 was released (5,929,913 lines of code).

Starting in 2004, the release process changed and new kernels started coming out on a regular schedule every 2–3 months, numbered 2.6.0, 2.6.1, up through 2.6.39.

On 21 July 2011 Linus Torvalds announced the release of Linux 3.0: "Gone are the 2.6.<bignum> days".[18] The version bump is not about major technological changes when compared to Linux 2.6.39;[19] it marks the kernel's 20th anniversary.[20] The time-based release process remained the same.

As of 2013, the Linux 3.10 release had 15,803,499 lines of code.[21]

Tanenbaum–Torvalds debate[edit]

The fact that Linux is a monolithic kernel rather than a microkernel was the topic of a debate between Andrew S. Tanenbaum, the creator of MINIX, and Linus Torvalds.[22] The debate, started in 1992 on the Usenet discussion group comp.os.minix, was about Linux and kernel architecture in general.[23] Tanenbaum argued that microkernels are superior to monolithic kernels and that therefore Linux is obsolete. Unlike traditional monolithic kernels, device drivers in Linux are easily configured as loadable kernel modules and are loaded or unloaded while running the system. This subject was revisited on 9 May 2006,[24] and on 12 May 2006 Tanenbaum wrote a position statement.[25]

Legal aspects[edit]

Licensing terms[edit]

Initially, Torvalds released Linux under a license which forbade any commercial use.[26] This was changed in version 0.12 to the GNU General Public License (GPL).[15] This license allows distribution and sale of possibly modified and unmodified versions of Linux but requires that all those copies be released under the same license and be accompanied by the complete corresponding source code.

Torvalds has described licensing Linux under the GPL as the "best thing I ever did."[26]

GPL version 3[edit]

Currently, Linux is licensed only under version 2 of the GPL,[5] without offering the licensee the option to choose "any later version", and there is some debate over how easily it could be changed to use later GPL versions such as version 3 (and whether this is even desirable).[27] Torvalds himself specifically indicated upon the release of version 2.4.0 that his own code is only under version 2.[28] However, the terms of the GPL state that if no version is specified, then any version may be used, and Alan Cox pointed out that very few other Linux contributors have specified a particular version of the GPL.[29] In September 2006, a survey of 29 key kernel programmers indicated 28 preferred GPLv2 to the then-current GPLv3 draft. Torvalds commented, "I think a number of outsiders... believed that I personally was just the odd man out, because I've been so publicly not a huge fan of the GPLv3."[30]

Loadable kernel modules[edit]

It is debated whether loadable kernel modules (LKMs) are to be considered derivative works under copyright law, and thereby fall under the terms of the GPL.

Torvalds has stated his belief that LKMs using only a limited, "public" subset of the kernel interfaces can sometimes be non-derived works, thus allowing some binary-only drivers and other LKMs that are not licensed under the GPL[citation needed]. A very good example for this is the usage of DMA_BUF by the proprietary NVidia graphics drivers. DMA_BUF is a recent kernel feature (like the rest of the kernel, it is licensed under the GPL) that allows multiple GPUs to quickly copy data into each other's framebuffers. One possible use case would be Nvidia Optimus that pairs a fast GPU with an Intel integrated GPU, where the NVIDIA GPU writes into the Intel framebuffer when it is active. But, NVIDIA cannot use this infrastructure because it uses a technical means to enforce the rule that it can only be used by LKMs that are also GPL. Alan Cox replied on LKML, rejecting a request from one of their engineers to remove this technical enforcement from the API.[31] Not all Linux kernel contributors agree with this interpretation, however, and even Torvalds agrees that many LKMs are clearly derived works, and indeed he writes that "kernel modules ARE derivative 'by default'".[32]

On the other hand Torvalds has also said that "one gray area in particular is something like a driver that was originally written for another operating system (i.e. clearly not a derived work of Linux in origin). [...] THAT is a gray area, and _that_ is the area where I personally believe that some modules may be considered to not be derived works simply because they weren't designed for Linux and don't depend on any special Linux behaviour."[33] Proprietary graphics drivers, in particular, are heavily discussed. Ultimately, it is likely that such questions can only be resolved by a court.

Kernel modules[edit]

Network
Graphics and general-purpose computing on graphics processing units
Sound
Input

Firmware binary blobs[edit]

One point of licensing controversy is Linux's use of firmware "binary blobs" to support several hardware devices. These files are under a variety of licenses, many of them restrictive and their exact underlying source code is usually unknown.[7] In the year 2002 Richard Stallman stated why, in his point of view, such blobs make Linux partially non-free software, and that distributing Linux "violates the GPL" (which requires "complete corresponding source code" to be available).[6] In 2008 Free Software Foundation Latin America started a project, Linux-libre, to create a completely free kernel without proprietary objects, which is used by some completely free distributions, such as those endorsed by the Free Software Foundation.[34][35] On 15 December 2010 the Debian Project announced that the next Debian stable version would come with a kernel "stripped of all non-free firmware bits".[36] This policy was continued with the sequel release of Debian 7 "Wheezy".

Trademark[edit]

Linux is a registered trademark of Linus Torvalds in the United States and some other countries. This is the result of an incident in which William Della Croce, Jr., who was not involved in the Linux project, trademarked the name and subsequently demanded royalties for its use.[37] Several Linux backers retained legal counsel and filed suit against Della Croce. The issue was settled in August 1997 when the trademark was assigned to Linus Torvalds.[38][39]

SCO litigation[edit]

For more details on this topic, see SCO-Linux controversies.

In March 2003, the SCO Group (SCO) filed a lawsuit against IBM claiming that IBM had violated copyrights that SCO claimed to hold over the Unix source code, by contributing portions of that code to Linux. Additionally, SCO sent letters to a number of companies warning that their use of Linux without a license from SCO may be a violation of copyright law, and claimed in the press that they would be suing individual Linux users. IBM then promised to defend its Linux customers on their behalf. This controversy has generated lawsuits by SCO against Novell, DaimlerChrysler (partially dismissed in July, 2004), and AutoZone, and retaliatory lawsuits by Red Hat and others against SCO.

In early 2007 SCO filed the specific details of the purported copyright infringement. Despite previous claims that SCO was the rightful owner of 1 million lines of code, they specified 326 lines of code, most of which were uncopyrightable.[40] In August 2007, the court in the Novell case ruled that SCO did not actually own the Unix copyrights to begin with,[41] though the Tenth Circuit Court of Appeals ruled in August 2009 that the question of who owned the copyright properly remained for a jury to answer.[42] The jury case was decided on 30 March 2010 in Novell's favour.[43]

Architecture[edit]

Map of the Linux kernel
The Linux kernel is ubiquitously found on various hardware and is supported by an abundance of both free and open-source and also proprietary software.
See also: vmlinux
Various layers within Linux, also showing separation between the userland and kernel space
User mode User applications e.g. bash, LibreOffice, Blender, 0 A.D.
Low-level system components: System daemons:
systemd, logind, networkd, soundd, ...
Windowing system:
display server
Other libraries:
GLib, GTK+, Qt, EFL, SDL, SFML, FLTK, GNUstep, etc.
Graphics:
Mesa 3D, AMD Catalyst, ...
C standard library open, exec, sbrk, socket, fopen, calloc, ... (up to 2000 subroutines)
glibc aims to be POSIX/SUS-compatible, uClibc targets embedded systems, bionic written for Android, etc.
Kernel mode Linux kernel stat, splice, dup, read, open, ioctl, write, mmap, close, exit, etc. (about 380 system calls)
The Linux kernel System Call Interface (SCI, aims to be POSIX/SUS-compatible)
Process scheduling
subsystem
IPC
subsystem
Memory management
subsystem
Virtual files
subsystem
Network
subsystem
Articles: ALSA, DRI, evdev, LVM, device mapper, Linux Network Scheduler, Netfilter
Linux Security Modules: SELinux, TOMOYO, AppArmor, Smack
Hardware (CPU, main memory, data storage devices, etc.)

Linux is a monolithic kernel. Device drivers and kernel extensions run in kernel space (ring 0 in many CPU architectures), with full access to the hardware, although some exceptions run in user space, for example filesystems based on FUSE. The graphics system most people use with Linux doesn't run in the kernel, in contrast to that found in Microsoft Windows. Unlike standard monolithic kernels, device drivers are easily configured as modules, and loaded or unloaded while running the system. Also unlike standard monolithic kernels, device drivers can be pre-empted under certain conditions. This latter feature was added to handle hardware interrupts correctly, and to improve support for symmetric multiprocessing.[citation needed] By choice, the Linux kernel has no Binary Kernel Interface.[44]

The hardware is also incorporated into the file hierarchy. Device drivers interface to user applications via an entry in the /dev[45] and/or /sys directories. Process information as well is mapped to the file system through the /proc directory.[45]

Linux supports true preemptive multitasking (both in user mode and kernel mode), virtual memory, shared libraries, demand loading, shared copy-on-write executables (via KSM), memory management, the Internet protocol suite, and threading.

Programming language[edit]

The Linux kernel is written in the version of the C programming language supported by GCC (which has introduced a number of extensions and changes to standard C), together with a number of short sections of code written in the assembly language (in GCC's "AT&T-style" syntax) of the target architecture. Because of the extensions to C it supports, GCC was for a long time the only compiler capable of correctly building the Linux kernel. In 2004, Intel claimed to have modified the kernel so that its C compiler also was capable of compiling it.[46] There was another such reported success in 2009 with a modified 2.6.22 version of the kernel.[47][48]

Since 2010, effort has been underway to build the Linux kernel with Clang, an alternative compiler for the C language;[49] as of 12 April 2014, the official kernel could almost be compiled by Clang.[50] The project dedicated to this effort is named LLVMLinux[51] after the LLVM compiler infrastructure upon which Clang is built. By enabling the Linux kernel to be compiled by Clang, which, among other advantages, is known for its fast compilation times against GCC, the kernel developers may benefit from a faster workflow due to shorter compilation times.[52]

Interfaces[edit]

Four interfaces are distinguished: two internal to the kernel, and two between the kernel and userspace.
Proprietary Linux graphic drivers like, e.g. the libGL-fglrx-glx bring their own proprietary binary blobs instead of utilizing the existent DRI/DRM. Because of the lack of a stable in-kernel ABI, this binary blobs have to be adapted to each and every change by the hardware developers themselves. On the GDC 2014, AMD was exploring a strategy change.[53]

Conformance to standards is a general policy for the Linux kernel's internals.

Kernel-to-userspace API[edit]

Main articles: POSIX and Single UNIX Specification

Source code portability ensures that a C program written by conforming to a standard can be successfully compiled and run on any system that also conforms to the same standard. The relevant standards, aiming to achieve source code portability of programs, that the development of the Linux kernel, the GNU C Library, and associated utilities tries to adhere to, are POSIX and the Single UNIX Specification. However, as of February 2014, no Linux distributions are branded as "UNIX" by The Open Group, mainly because of the costs of the conformance testing.

The Linux kernel API of the Linux kernel, representing the kernel's system call interface, is composed of the available system calls.

Kernel-to-userspace ABI[edit]

Main article: Linux Standard Base

Binary portability shall guarantee that any program once compiled for a given hardware platform, can be run in its compiled form on any other hardware platform that conforms to the standard. Binary portability is an essential requirement for the commercial viability of independent software vendor (ISV) applications built for the operating systems based on the Linux kernel. Binary compatibility is much more demanding than source code portability; as of February 2014, the only standard concerning itself with binary compatibility is the Linux Standard Base (LSB).

In-kernel API[edit]

There are a couple of kernel internal APIs utilized between the different subsystems and subsystems of subsystems. Some of them have been kept stable over several releases, other have not. There are no guarantees regarding the in-kernel APIs. Maintainers and contributors are free to augment or change them at any time.

Examples of in-kernel APIs include software frameworks/APIs for the following classes of device drivers:

In-kernel ABI[edit]

Strong interests in defining and maintaining a stable in-kernel ABI over several releases have been voiced repeatedly over time by parties, e.g. hardware manufactures, writing proprietary kernel modules and distributing binary-only software, e.g. device drivers.

By explicit choice the Linux kernel does not maintain a stable in-kernel ABI. The reasons are purely technical and not philosophical. Due to the absence of an in-kernel ABI that has to be kept stable over releases, the Linux kernel can keep a much higher rate of development.

Technical features[edit]

Preemption[edit]

The Linux kernel provides preemptive scheduling under certain conditions. Until kernel version 2.4, only user processes were preemptive, i.e., in addition to time quantum expiration, an execution of current process in user mode would be interrupted if higher dynamic priority processes entered TASK_RUNNING state.[55] Toward 2.6.x series of the Linux kernel, an ability to interrupt a task executing kernel code was added, although with that not all sections of the kernel code can be preempted.[56]

The Linux kernel contains different scheduler classes.[57] By default the kernel uses a scheduler mechanism called the Completely Fair Scheduler introduced in the 2.6.23 version of the kernel.[58] Internally this default-scheduler class is also known as SCHED_OTHER, but the kernel also contains two real-time scheduling classes named SCHED_FIFO (realtime first-in-first-out) and SCHED_RR (realtime round-robin) both of which take precedence over the default class.[57]

Through the use of the real-time Linux patch PREEMPT_RT, support for full preemption of critical sections, interrupt handlers, and "interrupt disable" code sequences can be supported.[59] Partial mainline integration of real-time Linux already brings some functionality to Linux mainline.[60] Preemption improves latency, increases responsiveness, and makes Linux more suitable for desktop and real-time applications. Older versions of the kernel had a so-called big kernel lock for synchronization across the entire kernel. This was finally removed by Arnd Bergmann in 2011.[61]

Additional scheduling policy known as SCHED_DEADLINE, implementing the earliest deadline first algorithm (EDF), was added to the Linux scheduler in version 3.14 of the Linux kernel mainline, released on 30 March 2014.[62][63]

Portability[edit]

iPod booting iPodLinux

While not originally designed to be portable,[13][64] Linux is now one of the most widely ported operating system kernels, running on a diverse range of systems from the ARM architecture to IBM Z/Architecture mainframe computers. The first port beyond Linux's original 386 architecture was to the Motorola 68000 platform by Amiga users, but to do this port they replaced major parts of the kernel, leading Torvalds to call it a fork and a "Linux-like operating system".[64] With this experience in mind, Torvalds led a major restructure of the kernel code to facilitate the next port effort, to the DEC Alpha AXP platform, and support both 386 and Alpha in a single source tree.[64]

Linux runs as the main operating system on IBM's Blue Gene supercomputers. As of June 2013, the Linux OS family has a 95.2% share of all systems on the TOP500 supercomputers list.[65] Linux has also been ported to various handheld devices such as TuxPhone, Apple's iPod and iPhone.[66] Some operating systems developed for mobile phones use modified versions of the Linux kernel, including Google Android, Firefox OS, HP webOS, and Nokia Maemo.[67][68][69]

Kernel panic[edit]

Kernel panic
Main article: Kernel panic

In Linux, a "panic" is an unrecoverable system error detected by the kernel, as opposed to similar errors detected by user space code. It is possible for kernel code to indicate such a condition by calling the panic function located in the header file sys/system.h. However, most panics are the result of unhandled processor exceptions in kernel code, such as references to invalid memory addresses. These are typically indicative of a bug somewhere in the call chain leading to the panic. They can also indicate a failure of hardware, such as a failed RAM cell or errors in arithmetic functions in the processor caused by a processor bug, overheating/damaged processor, or a soft error.

Kernel oops[edit]
Main article: Linux kernel oops

A report of a bug in the kernel is called an "OOPS".[70] These crash reports are automatically collected and can be sent upstream by various software, such as kerneloops,[71] ABRT (Fedora)[72] and apport (Ubuntu). KernelOops.org collected these reports and published statistics on their website.[73]

Security[edit]

Computer security is a much-publicized topic in relation to the Linux kernel, because a large number of bugs in the kernel can be potential security flaws, whether they allow privilege escalation or create denial-of-service attack vectors. Over the years, numerous such flaws were found and fixed in the Linux kernel.[74] New security features are continuously implemented to address computer insecurity issues in the Linux kernel.[75][76]

Critics have accused kernel developers of covering up security flaws or at least not announcing them. In response, in 2008, Linus Torvalds replied, "I personally consider security bugs to be just 'normal bugs'. I don't cover them up, but I also don't have any reason what-so-ever to think it's a good idea to track them and announce them as something special...one reason I refuse to bother with the whole security circus is that I think it glorifies—and thus encourages—the wrong behavior. It makes 'heroes' out of security people, as if the people who don't just fix normal bugs aren't as important. In fact, all the boring normal bugs are way more important, just because there's a lot more of them. I don't think some spectacular security hole should be glorified or cared about as being any more 'special' than a random spectacular crash due to bad locking."[77][78]

At times, bugs have been corrected in Linux before other systems. In May 2012, a difference between the implementations of the SYSRET instruction in AMD and Intel processors was found to cause vulnerabilities in major systems such as Windows, FreeBSD, XenServer, and Solaris. The issue had been fixed in the Linux kernel since 2006.[79]

Raw hardware devices are protected from direct access, and the file system has an inbuilt security system giving individual access to files on three levels, user only, group membership, and world access.[80]

Long term releases with constant security updates are also available for most distributions. Reboot-less security updates can even be applied to the kernel by using technologies such as ksplice.

Feature history[edit]

Version 1.0 of the Linux kernel was released on 14 March 1994.[81] This release of the Linux kernel only supported single-processor i386-based computer systems. Portability became a concern, and so version 1.2 (released 7 March 1995)[82] gained support for computer systems using processors based on the Alpha, SPARC, and MIPS architectures.

Version 2.0 was released 9 June 1996.[83] There were 41 releases in the series. The major feature of 2.0 was SMP support (that is, support for multiple processors in a single system) and support for more types of processors.

Version 2.2 (released 26 January 1999)[84] removed the global spinlock and provided improved SMP support, and added support for the m68k and PowerPC architectures as well as new file systems (including read-only support for Microsoft’s NTFS).[85]

Version 2.4.0, released on 4 January 2001,[86] contained support for ISA Plug and Play, USB, and PC Cards.[87] It also included support for the PA-RISC processor from Hewlett-Packard. Development for 2.4.x changed a bit in that more features were made available throughout the duration of the series, including: support for Bluetooth, Logical Volume Manager (LVM) version 1, RAID support, InterMezzo and ext3 file systems.

Version 2.6.0 was released on 18 December 2003.[88] The development for 2.6.x changed further towards including new features throughout the duration of the series. Among the changes that have been made in the 2.6 series are: integration of µClinux into the mainline kernel sources, PAE support, support for several new lines of CPUs, integration of ALSA into the mainline kernel sources, support for up to 232 users (up from 216), support for up to 229 process IDs (64-bit only, 32-bit arches still limited to 215),[89] substantially increased the number of device types and the number of devices of each type, improved 64-bit support, support for file systems which support file sizes of up to 16 terabytes, in-kernel preemption, support for the Native POSIX Thread Library (NPTL), User-mode Linux integration into the mainline kernel sources, SELinux integration into the mainline kernel sources, InfiniBand support, and considerably more. Also notable are the addition of several file systems throughout the 2.6.x releases: FUSE, JFS, XFS, ext4 and more. Details on the history of the 2.6 kernel series can be found in the ChangeLog files on the 2.6 kernel series source code release area[90] of kernel.org.

Version 3.0 was released on 22 July 2011.[91] Torvalds announced that the big change was, "NOTHING. Absolutely nothing."[92] 30 May 2011 saw Torvalds announce, "...let's make sure we really make the next release not just an all new shiny number, but a good kernel too." After the expected 6–7 week development process, it would be released near the 20th anniversary of Linux.[92]

In December 2012, Torvalds decided to reduce kernel complexity by removing support for i386 processors,[93] making the 3.7 kernel series the last one still supporting the original processor.[94] The same series unified support for the ARM processor.[95]

Version 3.11, released on 2 September 2013, adds many new features such as new O_TMPFILE flag for open(2) to reduce temporary file vulnerabilities, experimental AMD Radeon dynamic power management, low-latency network polling, and zswap (compressed swap cache).[96]

Development[edit]

The kernel changes made in year 2007 have been submitted by no less than 1900 developers – but there may be a lot more because developers working in teams usually count as one. It is generally assumed that the community of Linux kernel developers is composed by 5000 or 6000 members. As of 2013, the 3.10 release of the Linux kernel had 15,803,499 lines of code; without smart project management it would not be possible to keep such scale of development up and going.

  • Instead of a roadmap, there are technical guidelines. Instead of a central resource allocation, there are persons and companies who all have a stake in the further development of the Linux kernel, quite independently from one another:

People like Linus Torvalds and I don’t plan the kernel evolution. We don’t sit there and think up the roadmap for the next two years, then assign resources to the various new features. That’s because we don’t have any resources. The resources are all owned by the various corporations who use and contribute to Linux, as well as by the various independent contributors out there. It’s those people who own the resources who decide...

Andrew Morton, 2005
  • Linux is evolution, not intelligent design

    —Linus Torvalds, 2005[97][98]

The fact is, evolution often does odd (and "sub-optimal") things exactly because it does incremental changes which do not break at any point. It would be next to impossible to manage and coordinate all the development going on, to achieve set goals at set deadlines; instead, there are incremental changes, that by definition do not break at any point. As a result, any released version of the Linux kernel is fully usable, even if, for example, device drivers do not support all features of the hardware they are written for.

The conceptual architecture of the Linux kernel has proved its success; essential factors for this success were the provision for the organization of developers, and the provision for system extensibility. The Linux kernel's architecture was required to support a large number of independent volunteer developers; this requirement suggested that the system portions that require the most development—the hardware device drivers and the file and network protocols—be implemented in an extensible fashion. The Linux kernel's architecture chose to make these systems extensible using a data abstraction technique – each hardware device driver is implemented as a separate module that supports a common interface. In this way, a single developer can add a new device driver, with minimal interaction required with other developers of the Linux kernel. The success of the kernel implementation by a large number of volunteer developers proves the correctness of this strategy.

Another important extension to the Linux kernel is the addition of more supported hardware platforms. The architecture of the system supports this extensibility by separating all hardware-specific code into distinct modules within each subsystem. In this way, a small group of developers can implement a port of the Linux kernel to a new hardware architecture by re-implementing only the machine-specific portions of the kernel.

Estimated cost to redevelop[edit]

The cost to redevelop the Linux kernel version 2.6.0 in a traditional proprietary development setting has been estimated to be $612 million USD (€467 million euro, £394 million GBP) in 2004 prices using the COCOMO man-month estimation model.[99] In 2006, a study funded by the European Union put the redevelopment cost of kernel version 2.6.8 higher, at €882 million euro ($1.14 billion USD, £744 million GBP).[100]

This topic was revisited in October 2008 by Amanda McPherson, Brian Proffitt and Ron Hale-Evans. Using David A. Wheeler's methodology, they estimated redevelopment of the 2.6.25 kernel now costs $1.3 billion (part of a total $10.8 billion to redevelop Fedora 9).[101] Again, Garcia-Garcia and Alonso de Magdaleno from University of Oviedo (Spain) estimate that the value annually added to kernel was about 100 million EUR between 2005 and 2007 and 225 million EUR in 2008, it would cost also more than one billion EUR (about 1.4 billion USD) to develop in the European Union.[102]

As of 4 January 2011, using current LOC (lines of code) and wage numbers with David A. Wheeler's calculations it would cost approximately 3 billion USD (about 2.2 billion EUR) to redevelop the Linux kernel.[103]

Development model[edit]

The current development model of the Linux kernel is such that Linus Torvalds makes the releases of new versions, also called the "vanilla" or "mainline" kernels, meaning that they contain the main, generic branch of development. This branch is officially released as a new version approximately every ten weeks, after Torvalds does an initial round of integrating major changes made by all other programmers, and several rounds of bug-fix pre-releases.

In the current scheme, the main branch of development is not a traditional "stable" branch, instead it incorporates all kinds of changes, both the latest features as well as security and bug fixes. For users who do not want to risk updating to new versions containing code that may not be well tested, a separate set of "stable" branches exist, one for each released version, which are meant for people who just want the security and bug fixes, but not a whole new version. These branches are maintained by the stable team (Greg Kroah-Hartman, Chris Wright, and others).

The development model for Linux 2.6 was a significant change from the development model for Linux 2.5. Previously there was a stable branch (2.4) where only relatively minor and safe changes were merged, and an unstable branch (2.5), where bigger changes and cleanups were allowed. Both of these branches had been maintained by the same set of people, led by Torvalds. This meant that users would always have a well-tested 2.4 version with the latest security and bug fixes to use, though they would have to wait for the features which went into the 2.5 branch. The downside of this was that the "stable" kernel ended up so far behind that it no longer supported recent hardware and lacked needed features. In the late 2.5.x series kernel some maintainers elected to try and back port their changes to the stable series kernel which resulted in bugs being introduced into the 2.4.x series kernel. The 2.5 branch was then eventually declared stable and renamed to 2.6. But instead of opening an unstable 2.7 branch, the kernel developers decided to continue putting major changes into the 2.6 branch, which would then be released at a pace faster than 2.4.x but slower than 2.5.x. This had the desirable effect of making new features more quickly available and getting more testing of the new code, which was added in smaller batches and easier to test.

As a response to the lack of a stable kernel tree where people could coordinate the collection of bug fixes as such, in December 2005 Adrian Bunk announced that he would keep releasing 2.6.16.y kernels when the stable team moved on to 2.6.17.[104] He also included some driver updates, making the maintenance of the 2.6.16 series very similar to the old rules for maintenance of a stable series such as 2.4.[105] Since then, the "stable team" had been formed, and it would keep updating kernel versions with bug fixes. In October 2008 Adrian Bunk announced that he will maintain 2.6.27 for a few years as a replacement of 2.6.16.[106] The stable team picked up on the idea[107] and as of 2010 they continue to maintain that version and release bug fixes for it, in addition to others.

After the change of the development model with 2.6.x, developers continued to want what one might call an unstable kernel tree, one that changes as rapidly as new patches come in. Andrew Morton decided to repurpose his -mm tree from memory management to serve as the destination for all new and experimental code. In September 2007 Morton decided to stop maintaining this tree.[108] In February 2008, Stephen Rothwell created the linux-next tree to serve as a place where patches aimed to be merged during the next development cycle are gathered.[109][110] Several subsystem maintainers also adopted the suffix -next for trees containing code which is meant to be submitted for inclusion in the next release cycle.

As of January 2014 the currently in-development version of the Linux kernel is held in an unstable branch named linux-next.[111]

Relation with Linux distributions[edit]

Most Linux users run a kernel supplied by their Linux distribution. Some distributions ship the "vanilla" and/or "stable" kernels. However, several Linux distribution vendors (such as Red Hat and Debian) maintain another set of Linux kernel branches which are integrated into their products. These are by and large updated at a slower pace compared to the "vanilla" branch, and they usually include all fixes from the relevant "stable" branch, but at the same time they can also add support for drivers or features which had not been released in the "vanilla" version the distribution vendor started basing their branch from.

Maintenance[edit]

While Linus Torvalds supervises code changes and releases to the latest kernel versions, he has delegated the maintenance of older versions to other programmers.[112] Major releases as old as 2.0 (officially made obsolete with the kernel 2.2.0 release in January 1999) are maintained as needed, although at a very slow pace.

Kernel series Original release date Current version Maintainer Support Model
Old version, no longer supported: 0.01 17 September 1991 0.03 EOL
Old version, no longer supported: 0.10 November 1991 0.12 EOL
Old version, no longer supported: 0.95 8 March 1992 0.99.15 EOL
Old version, no longer supported: 1.0 14 March 1994 1.0.9 EOL
Old version, no longer supported: 1.1 6 April 1994 1.1.95 EOL
Old version, no longer supported: 1.2 7 March 1995 1.2.13 EOL
Old version, no longer supported: 1.3 12 June 1995 1.3.100 EOL
Old version, no longer supported: pre2.0 12 May 1996 pre2.0.14 EOL
Old version, no longer supported: 2.0 9 June 1996 2.0.40[113] David Weinehall EOL (Officially made obsolete with the kernel 2.2.0 release)[114]
Old version, no longer supported: 2.2 26 January 1999 2.2.26[115] Marc-Christian Petersen (formerly Alan Cox) EOL (Unofficially obsolete with the 2.2.27-rc2)[116][117]
Old version, no longer supported: 2.4 4 January 2001 2.4.37.11 Willy Tarreau (formerly Marcelo Tosatti) EOL (Maintained from December 2008 to December 2011), last stable release of the 2.4 kernel series.[118]
Old version, no longer supported: 2.6 18 December 2003 2.6.15 EOL
Old version, no longer supported: 2.6.16 20 March 2006 2.6.16.62 Adrian Bunk[119] (formerly Greg Kroah-Hartman)[120] EOL (First long-term stable release from March 2006 to July 2008)[121]
Old version, no longer supported: 2.6.27 9 October 2008[122] 2.6.27.62[123] Willy Tarreau[124] (formerly Greg Kroah-Hartman)[120] EOL (Second long-term stable release from October 2008 to March 2012)[125]
Older version, yet still supported: 2.6.32 2 December 2009[126] 2.6.32.63[127] Willy Tarreau[128][129] (formerly Greg Kroah-Hartman)[120][130] Third long-term stable release from December 2009 to mid-2015,[128] used in Debian 6 Squeeze.[131] Canonical will also provide support until April 2015.[132]
Old version, no longer supported: 2.6.33 24 February 2010[133] 2.6.33.20[134] Greg Kroah-Hartman[135] EOL (Fourth long-term stable release from March 2011 to November 2011). Base for Real-Time-Tree, replaced by 3.0.x[134][135]
Old version, no longer supported: 2.6.34 16 May 2010[136] 2.6.34.15[137] Paul Gortmaker[138] EOL (Fifth long-term stable release from January 2011 to February 2014)[138]
Old version, no longer supported: 2.6.35 1 August 2010[139] 2.6.35.14[140] Andi Kleen[141] EOL (Sixth long-term stable release from December 2010 to March 2012)[141]
Old version, no longer supported: 2.6.39 18 May 2011[142] 2.6.39.4[143] Greg Kroah-Hartman EOL (Maintained from May 2011 to August 2011), last stable release of the 2.6 kernel series.[143]
Old version, no longer supported: 3.0 21 July 2011[91] 3.0.101[144] Greg Kroah-Hartman[145] EOL (Seventh long-term stable release from July 2011 to October 2013 (Base for Real-Time-Tree))[145]
Old version, no longer supported: 3.1 24 October 2011[146] 3.1.10[147] Greg Kroah-Hartman EOL (Maintained from October 2011 to January 2012)[147]
Older version, yet still supported: 3.2 4 January 2012[148] 3.2.61[149] Ben Hutchings[128][150] Eighth long-term stable release from March 2012 to 2016, used in Ubuntu 12.04 LTS, Debian 7 Wheezy and Slackware 14.0.[128][150] Canonical will provide extended support until April 2017.[132]
Old version, no longer supported: 3.3 18 March 2012[151] 3.3.8[152] Greg Kroah-Hartman EOL (Maintained from March 2012 to June 2012)[152]
Older version, yet still supported: 3.4 20 May 2012[153][154] 3.4.98[155] Greg Kroah-Hartman[128][156] Ninth long-term stable release from May 2012 to October 2014[128][156]
Old version, no longer supported: 3.5 21 July 2012[157] 3.5.7[158] Greg Kroah-Hartman EOL (Maintained by Kroah-Hartman until the release of 3.6.1, from July 2012 to October 2012).[158] Canonical provides extended support until April 2014.[132][159]
Old version, no longer supported: 3.6 30 September 2012[160] 3.6.11[161] Greg Kroah-Hartman EOL (Maintained from October 2012 to December 2012)[161]
Old version, no longer supported: 3.7 10 December 2012[162] 3.7.10[163] Greg Kroah-Hartman EOL (Maintained from December 2012 to March 2013)[163][164]
Old version, no longer supported: 3.8 18 February 2013[165] 3.8.13[166] Greg Kroah-Hartman EOL (Maintained from February 2013 to May 2013).[166] Canonical provides extended support until August 2014.[132][167]
Old version, no longer supported: 3.9 28 April 2013[168] 3.9.11[169] Greg Kroah-Hartman EOL (Maintained from April 2013 to July 2013)[169]
Older version, yet still supported: 3.10 30 June 2013[170] 3.10.47[171] Greg Kroah-Hartman[128] Tenth long-term stable release from August 2013 to September 2015.[128][172]
Old version, no longer supported: 3.11 2 September 2013[173] 3.11.10[174] Greg Kroah-Hartman EOL (Maintained from September 2013 to November 2013).[174] Canonical provides extended support until August 2014.[132]
Older version, yet still supported: 3.12 3 November 2013[175] 3.12.24[176] Jiří Slabý[128] (formerly Greg Kroah-Hartman)[177] Eleventh long-term stable release from November 2013 to 2016[128]
Old version, no longer supported: 3.13 19 January 2014[178] 3.13.11[179] Greg Kroah-Hartman EOL (Maintained from January 2014 to April 2014).[179] Canonical provides extended support until April 2016.[132][180]
Older version, yet still supported: 3.14 30 March 2014[181] 3.14.12[182] Greg Kroah-Hartman[128] Twelfth long-term stable release from March 2014 to August 2016[128]
Current stable version: 3.15 8 June 2014[183] 3.15.5[184] Greg Kroah-Hartman Latest stable version.
Latest preview version of a future release: 3.16 16 June 2014[185] 3.16-rc4[186] Linus Torvalds Latest unstable version.
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

Revision control[edit]

The Linux kernel source code used to be maintained without the help of an automated source code management system, mostly because of Linus Torvalds' dislike of centralized SCM systems.

In 2002, Linux kernel development switched to BitKeeper, an SCM system which satisfied Linus Torvalds' technical requirements. BitKeeper was made available to Linus and several others free of charge, but was not free software, which was a source of controversy. The system did provide some interoperability with free SCM systems such as CVS and Subversion.

In April 2005, however, efforts to reverse-engineer the BitKeeper system by Andrew Tridgell led BitMover, the company which maintained BitKeeper, to stop supporting the Linux development community. In response, Linus Torvalds and others wrote a new source code control system for the purpose, called Git. The new system was written within weeks, and in two months the first official kernel release was made using Git.[187] Git soon developed into a separate project in its own right and gained wide adoption in the free software community.

Version numbering[edit]

The Linux kernel has had three different numbering schemes.

The first scheme was used in the run-up to "1.0". The first version of the kernel was 0.01. This was followed by 0.02, 0.03, 0.10, 0.11, 0.12 (the first GPL version), 0.95, 0.96, 0.97, 0.98, 0.99 and then 1.0.[188] From 0.95 on there were many patch releases between versions.

After the 1.0 release and prior to version 2.6, the number was composed as "A.B.C", where the number A denoted the kernel version, the number B denoted the major revision of the kernel, and the number C indicated the minor revision of the kernel. The kernel version was changed only when major changes in the code and the concept of the kernel occurred, twice in the history of the kernel: in 1994 (version 1.0) and in 1996 (version 2.0). Version 3.0 was released in 2011, but it was not a major change in kernel concept. The major revision was assigned according to the traditional even-odd system version numbering system. The minor revision had been changed whenever security patches, bug fixes, new features or drivers were implemented in the kernel.

In 2004, after version 2.6.0 was released, the kernel developers held several discussions regarding the release and version scheme[189][190] and ultimately Linus Torvalds and others decided that a much shorter "time-based" release cycle would be beneficial. For about seven years, the first two numbers remained "2.6", and the third number was incremented with each new release, which rolled out after two to three months. A fourth number was sometimes added to account for bug and security fixes (only) to the kernel version. The even-odd system of alternation between stable and unstable was gone. Instead, development pre-releases are titled release candidates, which is indicated by appending the suffix '-rc' to the kernel version, followed by an ordinal number.

The first use of the fourth number occurred when a grave error, which required immediate fixing, was encountered in 2.6.8's NFS code. However, there were not enough other changes to legitimize the release of a new minor revision (which would have been 2.6.9). So, 2.6.8.1 was released, with the only change being the fix of that error. With 2.6.11, this was adopted as the new official versioning policy. Later it became customary to continuously back-port major bug-fixes and security patches to released kernels and indicate that by updating the fourth number.

On 29 May 2011, Linus Torvalds announced[191] that the kernel version would be bumped to 3.0 for the release following 2.6.39, due to the minor version number getting too large and to commemorate the 20th anniversary of Linux. It continued the time-based release practice introduced with 2.6.0, but using the second number—e.g. 3.1 would follow 3.0 after a few months. An additional number (now the third number) would be added on when necessary to designate security and bug fixes, as for example with 3.0.18. As of 30 March 2014, the latest stable version is 3.14. The major version number might be raised to 4 at some future date.[192]

In addition to Linus's "-rc" development releases, sometimes the version will have a suffix such as "tip", indicating another development branch, usually (but not always) the initials of a person who made it. For example, "ck" stands for Con Kolivas, "ac" stands for Alan Cox, etc. Sometimes, the letters are related to the primary development area of the branch the kernel is built from, for example, "wl" indicates a wireless networking test build. Also, distributors may have their own suffixes with different numbering systems and for back-ports to their "enterprise" (i.e. stable but older) distribution versions.

Timeline[edit]

Variants[edit]

Variants of the Linux kernel include the following:

See also[edit]

References[edit]

  1. ^ Linux Online (2008). "Linux Logos and Mascots". Archived from the original on 15 August 2010. Retrieved 11 August 2009. 
  2. ^ "The linux-kernel mailing list FAQ". Tux.Org. 
  3. ^ "Linux 3.15.6". Linux kernel mailing list. 17 July 2014. //https://lkml.org/lkml/2014/7/17/703.
  4. ^ InfoWorld. "Linux creator Torvalds still no fan of GPLv3". Retrieved 2008-10-11. 
  5. ^ a b c "Linux Kernel Copying". Retrieved 2013-09-25. 
  6. ^ a b Stallman, Richard (2002). "Linux, GNU, and freedom". Free Software Foundation. Retrieved 2007-02-21. 
  7. ^ a b c "linux/kernel/git/stable/linux-stable.git/blob - firmware/WHENCE". git.kernel.org. 2002-10-16. Retrieved 2012-08-21. 
  8. ^ "README". git.kernel.org. Retrieved 2010-11-12. 
  9. ^ Linus Torvalds (2006-09-25). "Re: GPLv3 Position Statement". 
  10. ^ Marjorie Richardson (1 November 1999). "Interview: Linus Torvalds". Linux Journal. Retrieved 20 August 2009. 
  11. ^ "Free as in Freedom by Sam Williams. O'Reilly books, 2002". Oreilly.com. Retrieved 2010-11-12. 
  12. ^ Greg Kroah-Hartman (April 2008). "Linux Kernel Development: How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It". "Since 2005, over 3700 individual developers from over 200 different companies have contributed to the kernel." 
  13. ^ a b Torvalds, Linus Benedict. "What would you like to see most in minix?". comp.os.minix. Web link.
  14. ^ Torvalds, Linus Benedict. "Free minix-like kernel sources for 386-AT". comp.os.minix. Web link.
  15. ^ a b Torvalds, Linus. "Release Notes for Linux v0.12". The Linux Kernel Archives. Retrieved 2007-02-21. 
  16. ^ Summers, David W (19 January 1992). "Troubles with Partitions". comp.os.minix. Web link. Retrieved 2007-01-07.
  17. ^ Clegg, Alan B (31 March 1992). "It's here!". comp.os.linux. Web link. Retrieved 2007-01-07.
  18. ^ Linus Torvalds (Thu, 21 Jul 2011 19:59:53 -0700). "Linux 3.0 release". Linux Kernel Mailing List. 
  19. ^ "Linux Kernel Data". Archived from the original on 23 May 2011. 
  20. ^ Mark Hachman (22 July 2011). "Linux 3.0 Released; Linus Torvalds Explains Why You Shouldn't Care". PC Magazine. 
  21. ^ Leemhuis, Thorsten (1 July 2013). "What's new in Linux 3.10". The H. Heinz Heise. Archived from the original on 4 July 2013. Retrieved 15 July 2013. 
  22. ^ O'Reilly (1999). "The Tanenbaum-Torvalds Debate". O'Reilly. Retrieved 2006-11-22. 
  23. ^ Tanenbaum, Andy (29 January 1992). "LINUX is obsolete". comp.os.minix. Web link. Retrieved 2006-05-10.
  24. ^ Torvalds, Linus (9 May 2006). "Hybrid kernel, not NT". Retrieved 2007-01-06. 
  25. ^ Tanenbaum, Andy (12 May 2006). "Tanenbaum-Torvalds Debate: Part II". Retrieved 2007-01-06. 
  26. ^ a b Yamagata, Hiroo (1997). "The Pragmatist of Free Software". HotWired. Archived from the original on 2007-02-10. Retrieved 2007-02-21. 
  27. ^ Corbet, Jonathan (2006-01-31). "GPLv3 and the kernel". LWN.net. Retrieved 2007-02-21. 
  28. ^ Torvalds, Linus (2000-09-08). "Linux-2.4.0-test8". Linux-kernel mailing list archive. Unix Systems Support Group of Indiana University. Retrieved 2007-02-21. 
  29. ^ Cox, Alan (2006-01-20). "Re: GPL V3 and Linux". Linux-kernel mailing list archive. LWN.net. Retrieved 2007-02-21. 
  30. ^ Shankland, Stephen (25 September 2006). "Top Linux programmers pan GPL 3". News.com. Retrieved 2007-02-21. 
  31. ^ "[PATCH] dma-buf: Use EXPORT_SYMBOL". 2012-10-10. 
  32. ^ Linus Torvalds (2003-12-10). "RE: Linux GPL and binary module exception clause?". 
  33. ^ Linus Torvalds <torvalds@osdl.org> (2003-12-03). "Re: Linux GPL and binary module exception clause?". Ussg.iu.edu. Retrieved 2010-11-12. 
  34. ^ "Linux-libre project". www.fsfla.org. Retrieved 2009-10-05. 
  35. ^ "Trisquel GNU/Linux-libre". trisquel.info. Retrieved 2009-10-05. 
  36. ^ "Debian 6.0 "Squeeze" to be released with completely free Linux Kernel". 
  37. ^ Hughes, Phil (1997-08-01). "Linux Trademark Dispute". Linux Journal. Retrieved 2010-12-08. 
  38. ^ Phil Hughes (1 Mar 1997). "Action Taken on Linux Trademark". Linux Journal. 
  39. ^ Tonya Gisselberg (2010). "The Trademark History of Linux, the Operating System". 
  40. ^ "Report from the Courthouse 7 March".  Groklaw article
  41. ^ "Court Rules: Novell owns the UNIX and UnixWare copyrights".  Groklaw article
  42. ^ Ryan, Justin (August 2009). "SCO Will Try Again". Retrieved 2009-08-30. 
  43. ^ Harvey, Tom (2010-03-30). "Jury says Novell owns Unix copyrights". The Salt Lake Tribune. MediaNews Group. Retrieved 2010-03-30. 
  44. ^ Kroah-Hartman, Greg. "The Linux Kernel Driver Interface". 
  45. ^ a b Nguyen, Binh (30 July 2004). "Linux Filesystem Hierarchy: Chapter 1. Linux Filesystem Hierarchy". The Linux Documentation Project. Retrieved 28 November 2012. 
  46. ^ Ingo A. Kubbilun (2004-06-02). "Linux kernel patch for Intel Compiler". Pyrillion.org. Retrieved 2010-11-12. 
  47. ^ "Slashdot | High Performance Linux Kernel Project — LinuxDNA". Linux.slashdot.org. Retrieved 2010-10-30. 
  48. ^ "LinuxDNA Supercharges Linux with the Intel C/C++ Compiler". Linux Journal. Retrieved 2010-10-30. 
  49. ^ Larabel, Michael (26 October 2010). "LLVM's Clang Is Onto Building The Linux Kernel". Journal (Phoronix). Retrieved 10 June 2014. 
  50. ^ Larabel, Michael (12 April 2014). "Linux 3.15 Can Almost Be Compiled Under LLVM's Clang". Journal (Phoronix). Retrieved 10 June 2014. 
  51. ^ "LLVMLinux". The Linux Foundation. Retrieved 10 June 2014. 
  52. ^ "LLVMLinux". The Linux Foundation. Retrieved 10 June 2014. 
  53. ^ "AMD exploring new Linux driver Strategy". 2014-03-22. Retrieved 2014-03-23. 
  54. ^ "mac80211 documentation". Retrieved 2014-06-08. 
  55. ^ Daniel P. Bovet; Marco Cesati (October 2000). "Chapter 10, Understanding the Linux Kernel". 
  56. ^ Anand Santhanam (23 Sep 2003). "Towards Linux 2.6, A look into the workings of the next new kernel". IBM Global Services. Archived from the original on 27 September 2013. 
  57. ^ a b Bar, Moshe. "The Linux Scheduler". Linux Journal. Retrieved 2012-04-14. 
  58. ^ Molnár, Ingo (2007-04-13). "[patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]". linux-kernel mailing list. http://lwn.net/Articles/230501/.
  59. ^ Paul McKenney. "A realtime preemption overview". LWN.net. 
  60. ^ "OSADL Project: Realtime Linux". www.osadl.org. Retrieved 2012-02-05. 
  61. ^ "git.kernel.org: BKL: that's all folks". 
  62. ^ "1.1. Deadline scheduling class for better real-time scheduling". Linux kernel 3.14. kernelnewbies.org. 2014-03-30. Retrieved 2014-04-02. 
  63. ^ [1] Phoronix, The Linux 3.14 Kernel Already Has Many Exciting Features
  64. ^ a b c Torvalds, Linus (1999). "The Linux edge". Open Sources: Voices from the Open Source Revolution. O'Reilly. 
  65. ^ "Category: Operating system Family". Top 500 Supercomputer Sites. June 2013. 
  66. ^ "Android Now Running On iPhone 3G". 2010-05-07. Retrieved 2010-07-11. 
  67. ^ Greg Kroah-Hartman (2010-02-02). "Android and the Linux kernel community". Retrieved 2010-02-03. "This means that any drivers written for Android hardware platforms, can not get merged into the main kernel tree because they have dependencies on code that only lives in Google's kernel tree, causing it to fail to build in the kernel.org tree. Because of this, Google has now prevented a large chunk of hardware drivers and platform code from ever getting merged into the main kernel tree. Effectively creating a kernel branch that a number of different vendors are now relying on." 
  68. ^ "Linux developer explains Android kernel code removal". ZDNet. 2010-02-02. Archived from the original on 6 February 2010. Retrieved 2010-02-03. 
  69. ^ "Maemo platform described as being based on Linux kernel". Maemo community. 2010-04-09. Retrieved 2010-04-09. 
  70. ^ "Linux-Kernel Archive: Re: what's an OOPS". Lkml.indiana.edu. Retrieved 2010-10-30. 
  71. ^ "kerneloops(8) - Linux man page". Linux.die.net. Retrieved 2010-10-30. 
  72. ^ "Features/ABRTF12". FedoraProject. 2009-08-03. Retrieved 2010-10-30. 
  73. ^ "Kerneloops.org". Kerneloops.org. Retrieved 2014-03-05. 
  74. ^ K.K. Mookhey, Nilesh Burghate and ISACA (2005). Linux-- Security, Audit and Control Features. ISACA. p. 14. ISBN 1-893209-78-4. 
  75. ^ Brian Hatch (2008). Hacking exposed Linux: Linux security secrets & solutions. McGraw Hill Professional. p. 524. ISBN 0-07-226257-5. 
  76. ^ Trent Jaeger (2008). Operating system security. Morgan & Claypool Publishers. p. 122. ISBN 1-59829-212-9. 
  77. ^ Jeremy Andrews (2008-07-16). "Security Bugs and Full Disclosure". Archived from the original on 19 July 2008. Retrieved 2010-12-31. 
  78. ^ Brad Spengler (2008-07-16). "Linux's unofficial security-through-coverup policy". Full-Disclosure mailing list. http://seclists.org/fulldisclosure/2008/Jul/276. Retrieved 2010-12-31.
  79. ^ "The Intel SYSRET privilege escalation –". Blog.xen.org. 2012-06-13. Retrieved 2012-07-26. 
  80. ^ Anderson, Gareth (15 April 2006). "GNU/Linux Command-Line Tools Summary". The Linux Documentation Project. Retrieved 28 November 2012. 
  81. ^ "Kernel 1.0 Source Code Release". Retrieved 2008-10-27. 
  82. ^ "Kernel 1.2 Source Code Release". Retrieved 2008-10-27. 
  83. ^ "Kernel 2.0.x Source Code Releases". Retrieved 2008-10-27. 
  84. ^ "Kernel 2.2.x Source Code Releases". Retrieved 2008-10-27. 
  85. ^ "The Wonderful World of Linux 2.2". Retrieved 2008-10-27. 
  86. ^ "Kernel 2.4.x Source Code Releases". Retrieved 2008-10-27. 
  87. ^ "The Wonderful World of Linux 2.4". Retrieved 2008-10-27. 
  88. ^ "Kernel 2.6.x.y Source Code Releases". Retrieved 2008-10-27. 
  89. ^ "proc(5) - Linux manual page" (see /proc/sys/kernel/pid_max). 
  90. ^ "Index of /pub/linux/kernel/v2.6". Kernel.org. Retrieved 2014-03-02. 
  91. ^ a b Torvalds, Linus (21 July 2011). "Linux 3.0 release". Linux kernel mailing list. Retrieved 16 May 2013. 
  92. ^ a b Torvalds, Linus (30 May 2011). "Linux 3.0-rc1". Linux kernel mailing list. Gmane. Retrieved 1 July 2013. 
  93. ^ Bhartiya, Swapnil. "Linux Kills Support For Intel's 386 Processors". Retrieved 13 December 2012. 
  94. ^ Vaughan, Steven J. (2012-12-13). "Good-Bye 386: Linux to drop support for i386 chips with next major release". ZDNet. Retrieved 2013-02-06. 
  95. ^ Vaughan, Steven J. (2012-12-11). "Linux 3.7 arrives, ARM developers rejoice". ZDNet. Retrieved 2013-02-06. 
  96. ^ "Linux 3.11". kernelnewbies.org. 2013-09-02. Retrieved 2014-01-21. 
  97. ^ "Linux Evolution". 2008-03-26. 
  98. ^ "Perpetual Development: A Model of the Linux Kernel Life Cycle". 2011-10-25. 
  99. ^ David A. Wheeler. "Linux Kernel 2.6: It's Worth More!". 
  100. ^ "Economic impact of FLOSS on innovation and competitiveness of the EU ICT sector" (Table 3 on page 50). 
  101. ^ "Estimating Total Development Cost Of a Linux Distribution" (Table on page 6). 
  102. ^ "The Billion Dollar Kernel". Linux.slashdot.org. 2010-02-24. Retrieved 2010-11-12. 
  103. ^ Wheeler, David. "The Linux Kernel: It’s Worth More!". Retrieved 17 September 2012. 
  104. ^ Jeremy Offline (2001-10-13). "Linux: 2.6.16.y Lives On". KernelTrap. Retrieved 2010-10-30. 
  105. ^ Jeremy Offline (2001-10-13). "Linux: Maintaining A 2.6.16.y Tree". KernelTrap. Archived from the original on 20 June 2010. Retrieved 2010-10-30. 
  106. ^ "'Linux 2.6.27 will be a longtime supported kernel' - MARC". Marc.info. 2008-10-11. Retrieved 2010-10-30. 
  107. ^ Greg Kroah-Hartman (2009-09-08). "Re: 2.6.27 maintenance plans after 2.6.32 is released". linux-kernel mailing list. http://marc.info/?l=linux-kernel&m=125245118518458.
  108. ^ 2.6.23-rc6-mm1 "This Just Isn't Working Any More". KernelTrap. [dead link]
  109. ^ "Stephen Rothwell: Announce: Linux-next (Or Andrew's dream :-))". LKML. Retrieved 2010-10-30. 
  110. ^ "linux-next and patch management process". Lwn.net. 2010-10-21. Retrieved 2010-10-30. 
  111. ^ "The Linux Kernel Archives". Kernel.org. Retrieved 2014-01-22. 
  112. ^ See the Linux MAINTAINERS file. 
  113. ^ LATEST-IS-2.0.40. 
  114. ^ David Weinehall (2004-02-08). "[ANNOUNCE] Linux-kernel 2.0.40 aka ``The Moss-covered Tortoise". [dead link]
  115. ^ LATEST-IS-2.2.26. 
  116. ^ Marc-Christian Petersen (2005-01-13). "Linux 2.2.27-rc2". [dead link]
  117. ^ Marc-Christian Petersen (2004-02-25). "Linux 2.2.26". 
  118. ^ Willy Tarreau (2010-12-18). "Linux 2.4.37.11". Linux kernel mailing list. https://lkml.org/lkml/2010/12/18/73.
  119. ^ Kroah-Hartman, Greg (3 August 2006). "Adrian Bunk is now taking over the 2.6.16-stable branch". Linux kernel mailing list. https://lkml.org/lkml/2006/8/3/271.
  120. ^ a b c Kroah-Hartman, Greg (8 March 2012). "The 2.6.32 Linux kernel". Retrieved 1 June 2013. 
  121. ^ Bunk, Adrian (2008-10-11). "Linux 2.6.27 will be a longtime supported kernel". Linux kernel mailing list. http://marc.info/?l=linux-kernel&m=122375909403298.
  122. ^ Torvalds, Linus (9 October 2008). "Linux 2.6.27". Linux kernel mailing list. https://lkml.org/lkml/2008/10/9/415.
  123. ^ Tarreau, Willy (17 March 2012). "Linux 2.6.27.62". Linux kernel mailing list. https://lkml.org/lkml/2012/3/17/38.
  124. ^ Kroah-Hartman, Greg (12 December 2010). "Willy Tarreau is taking over the 2.6.27-longterm kernel release". Linux kernel mailing list. https://lkml.org/lkml/2010/12/12/140.
  125. ^ "Linux 2 6 27 - Linux Kernel Newbies". Kernelnewbies. Retrieved 2010-10-30. 
  126. ^ Torvalds, Linus (2 December 2009). "Linux 2.6.32". Linux kernel mailing list. https://lkml.org/lkml/2009/12/3/11.
  127. ^ Tarreau, Willy (19 June 2014). "Linux 2.6.32.63". Linux kernel mailing list. https://lkml.org/lkml/2014/6/18/710.
  128. ^ a b c d e f g h i j k l "Active kernel releases". Kernel.org. 6 August 2013. Retrieved 3 Jul 2014. 
  129. ^ Tarreau, Willy (5 March 2012). "Re: Linux 2.6.32.58". Linux kernel mailing list. https://lkml.org/lkml/2012/3/4/141.
  130. ^ Walker-Morgan, Dj (5 March 2012). "Maintenance of Linux kernel 2.6.32 is slowing down". The H Open. Heinz Heise. Retrieved 17 May 2013. [dead link]
  131. ^ "Package: linux-image-2.6-686 (2.6.32+29)". Debian.org. Retrieved 09 July 2014. 
  132. ^ a b c d e f "Ubuntu Kernel Team Extended Support". Ubuntu wiki. Canonical Ltd. Retrieved 30 Aug 2013. 
  133. ^ Torvalds, Linus (24 February 2010). "Linux 2.6.33 released". Linux kernel mailing list. https://lkml.org/lkml/2010/2/24/301.
  134. ^ a b Kroah-Hartman, Greg (7 November 2011). "Linux 2.6.33.20". Linux kernel mailing list. http://article.gmane.org/gmane.linux.kernel/1212299.
  135. ^ a b Leemhuis, Thorsten (23 March 2011). "Kernel Log: Development of 2.6.39 under way, series 33 revived". The H Open. Heinz Heise. Retrieved 17 May 2013. [dead link]
  136. ^ Torvalds, Linus (16 May 2010). "Linux 2.6.34". Linux kernel mailing list. https://lkml.org/lkml/2010/5/16/89.
  137. ^ Gortmaker, Paul (11 February 2014). "Linux 2.6.34.15". Linux kernel mailing list. https://lkml.org/lkml/2014/2/11/368.
  138. ^ a b Gortmaker, Paul (3 December 2010). "Announcement: Plans for v2.6.34-longterm". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1012.0/01338.html.
  139. ^ Torvalds, Linus (1 August 2010). "Linux 2.6.35". Linux kernel mailing list. https://lkml.org/lkml/2010/8/1/188.
  140. ^ Kleen, Andi (1 August 2011). "[ANNOUNCE The longterm Linux 2.6.35.14 kernel is released"]. Linux kernel mailing list. https://lkml.org/lkml/2011/8/1/324.
  141. ^ a b Kleen, Andi (3 December 2010). "Plans for 2.6.35-longterm was Re: Linux stable kernel release procedure changes". Linux Kernel Mailing List. Retrieved 17 May 2013. 
  142. ^ Torvalds, Linus (18 May 2011). "Linux 2.6.39". Linux kernel mailing list. https://lkml.org/lkml/2011/5/19/16.
  143. ^ a b Kroah-Hartman, Greg (3 August 2011). "Linux 2.6.39.4". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1108.0/01203.html.
  144. ^ Kroah-Hartman, Greg (22 October 2013). "Linux 3.0.101". Linux kernel mailing list. https://lkml.org/lkml/2013/10/22/125.
  145. ^ a b Leemhuis, Thorsten (12 January 2012). "Kernel Log: 15,000,000 lines, 3.0 promoted to long-term kernel". The H Open. Heinz Heise. Retrieved 27 Mar 2012. [dead link]
  146. ^ Torvalds, Linus (24 October 2011). "Linux 3.1". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1110.3/00210.html.
  147. ^ a b Kroah-Hartman, Greg (18 January 2012). "Linux 3.1.10". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1201.2/01340.html.
  148. ^ Torvalds, Linus (4 January 2012). "Linux 3.2". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1201.0/01228.html.
  149. ^ Hutchings, Ben (11 July 2014). "Linux 3.2.61". Linux kernel mailing list. https://lkml.org/lkml/2014/7/12/81.
  150. ^ a b von Eitzen, Chris (23 April 2012). "Long-term maintenance for Linux 3.2". The H Open. Heinz Heise. Retrieved 14 May 2013. [dead link]
  151. ^ Torvalds, Linus (18 March 2012). "Linux 3.3 release". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1203.2/00881.html.
  152. ^ a b Kroah-Hartman, Greg (4 June 2012). "Linux 3.3.8". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1206.0/01162.html.
  153. ^ Torvalds, Linus (20 May 2012). "Linux 3.4 released". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1205.2/02545.html.
  154. ^ Larabel, Michael (21 May 2012). "Linux 3.4 Kernel Released With Many New Features". Phoronix. Retrieved 1 July 2013. 
  155. ^ Kroah-Hartman, Greg (9 July 2014). "Linux 3.4.98". Linux kernel mailing list. https://lkml.org/lkml/2014/7/9/696.
  156. ^ a b Larabel, Michael (20 August 2012). "Linux 3.4 Kernel Will Be Supported For The Long-Term". Phoronix. Retrieved 12 Dec 2012. 
  157. ^ Torvalds, Linus (21 July 2012). "Linux 3.5 released". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1207.2/02998.html.
  158. ^ a b Kroah-Hartman, Greg (12 October 2013). "Linux 3.5.7". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1210.1/03204.html.
  159. ^ Krzesinski, Herton Ronaldo (9 November 2012). "Linux 3.6.11". Linux kernel mailing list. https://lkml.org/lkml/2012/11/9/184.
  160. ^ Torvalds, Linus (30 September 2012). "Linux 3.6". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1209.3/04237.html.
  161. ^ a b Kroah-Hartman, Greg (17 December 2012). "Linux 3.6.11". Linux kernel mailing list. https://lkml.org/lkml/2012/12/17/353.
  162. ^ Torvalds, Linus (10 December 2012). "Linux 3.7". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1212.1/01005.html.
  163. ^ a b Kroah-Hartman, Greg (27 February 2013). "Linux 3.7.10". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1302.3/01806.html.
  164. ^ Stahie, Silviu (1 March 2013). "Linux Kernel 3.7.10 Officially Reaches End of Life, Kernel.org Website Updated". Softpedia. Retrieved 1 Mar 2013. 
  165. ^ Torvalds, Linus (18 February 2013). "Linux 3.8". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1302.2/00936.html.
  166. ^ a b Kroah-Hartman, Greg (11 May 2013). "Linux 3.8.13". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1305.1/02171.html.
  167. ^ Walker-Morgan, DJ (15 May 2013). "Canonical to maintain Linux 3.8 until August 2014". The H Open. Heinz Heise. Retrieved 17 May 2013. [dead link]
  168. ^ Torvalds, Linus (28 April 2013). "Linux 3.9 released". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1304.3/02009.html.
  169. ^ a b Kroah-Hartman, Greg (21 July 2013). "Linux 3.9.11". Linux kernel mailing list. https://lkml.org/lkml/2013/7/21/178.
  170. ^ Torvalds, Linus (30 June 2013). "Linux 3.10". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1306.3/04336.html.
  171. ^ Kroah-Hartman, Greg (7 July 2014). "Linux 3.10.47". Linux kernel mailing list. https://lkml.org/lkml/2014/7/6/199.
  172. ^ "Longterm kernel 3.10 - Linux Kernel Monkey Log". 
  173. ^ Torvalds, Linus (2 September 2013). "Linux 3.11". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1309.0/00650.html.
  174. ^ a b Kroah-Hartman, Greg (29 November 2013). "Linux 3.11.10". Linux kernel mailing list. https://lkml.org/lkml/2013/11/29/327.
  175. ^ Torvalds, Linus (3 November 2013). "Linux 3.12 released .. and no merge window yet .. and 4.0 plans?". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1311.0/00914.html.
  176. ^ Slabý, Jiří (7 July 2014). "Linux 3.12.24". Linux kernel mailing list. https://lkml.org/lkml/2014/7/5/159.
  177. ^ Kroah-Hartman, Greg (26 February 2014). "3.12-stable kernel tree being taken over by Jiří Slabý". Linux kernel mailing list. https://lkml.org/lkml/2014/2/26/596.
  178. ^ Torvalds, Linus (19 January 2014). "Linux 3.13". Linux kernel mailing list. http://lkml.indiana.edu/hypermail/linux/kernel/1401.2/01593.html.
  179. ^ a b Kroah-Hartman, Greg (23 April 2014). "Linux 3.13.11". Linux kernel mailing list. https://lkml.org/lkml/2014/4/22/899.
  180. ^ "[ANNOUNCE Linux 3.13.y.z extended stable support"]. Linux kernel mailing list. 24 April 2014. https://lkml.org/lkml/2014/4/23/516.
  181. ^ Torvalds, Linus (30 March 2014). "Linux 3.14". Linux kernel mailing list. https://lkml.org/lkml/2014/3/30/336.
  182. ^ Kroah-Hartman, Greg (9 July 2014). "Linux 3.14.12". Linux kernel mailing list. https://lkml.org/lkml/2014/7/6/203.
  183. ^ Torvalds, Linus (9 July 2014). "Linux 3.15". Linux kernel mailing list. https://lkml.org/lkml/2014/6/8/70.
  184. ^ Kroah-Hartman, Greg (7 July 2014). "Linux 3.15.5". Linux kernel mailing list. https://lkml.org/lkml/2014/7/9/739.
  185. ^ Torvalds, Linus (27 June 2014). "Linux 3.16". Linux kernel mailing list. https://lkml.org/lkml/2014/6/16/1.
  186. ^ Torvalds, Linux (6 July 2014). "Linux 3.16-rc4". Linux kernel mailing list. https://lkml.org/lkml/2014/7/6/150.
  187. ^ Linux Kernel Mailing List (2005-06-17). "Linux 2.6.12". 
  188. ^ Riley Williams. "Linux Kernel Archives - Volume 1". 
  189. ^ Jeremy Offline (2001-10-13). "Kernel Release Numbering Redux". KernelTrap. Retrieved 2010-10-30. [dead link]
  190. ^ "Linus Torvalds: RFD: Kernel release numbering". LKML. Retrieved 2010-10-30. 
  191. ^ Linus Torvalds (2011-05-29). "Linux 3.0-rc1". Retrieved 2011-08-16. 
  192. ^ "Linus Torvalds: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?". LKML. Retrieved 2014-01-22. 

Further reading[edit]

External links[edit]