Linux kernel

From Seo Wiki - Search Engine Optimization and Programming Languages

Jump to: navigation, search
Linux kernel booting
Original author(s) Linus Torvalds
Developer(s) Linus Torvalds and thousands of collaborators
Initial release 1991
Written in C
Operating system Unix-like
Available in English
Type Kernel
License GNU General Public License version 2 (only)[1][2] plus proprietary binary blobs

The Linux kernel is an operating system kernel used by the Linux family of Unix-like operating systems.[3] It is one of the most prominent examples of free and open source software.[4]

The Linux kernel is released under the GNU General Public License version 2 (GPLv2),[2] plus proprietary licenses for some controversial binary blobs, and is developed by contributors worldwide. Day-to-day development takes place on the Linux kernel mailing list.

The Linux kernel was initially conceived and created by Finnish computer science student[5] Linus Torvalds in 1991. Linux rapidly accumulated developers and users who adopted code from other free software projects for use with the new operating system.[6] The Linux kernel has received contributions from thousands of programmers.[7] Many Linux distributions have been released based upon the Linux kernel.



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. Then, on 26 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.[8]

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, uploading it to the FTP server ( of the Helsinki University of Technology (HUT). It had 10,239 lines of code. In October 1991, Linux version 0.02 was released.[9]

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.[10]

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

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).
  • 3 December 2009 - Linux 2.6.32 was released (12,606,910 lines of code).[13]
Microsoft contributions

In July 2009 Microsoft contributed 20,000 lines of code to the Linux kernel. The contribution consisted of Hyper-V drivers, which improve the performance of virtual Linux guest systems in a Windows hosted environment. Microsoft licensed its Linux Hyper-V drivers under the GPL. Microsoft was forced to make the code contribution when Vyatta principal engineer and Linux contributor Stephen Hemminger discovered that Microsoft had incorporated a Hyper-V network driver, with GPL-licensed open source components, statically linked to closed-source binaries in contravention of the GPL license. Microsoft contributed the drivers to rectify the licence violation, although the company attempted to portray it as a charitable act, rather than one to avoid legal action against it. In the past Microsoft had termed Linux a "cancer" and "communist".[14][15][16][17]

Legal aspects

Licensing terms

Initially, Torvalds released Linux under a license which forbade any commercial exploitation. This was soon changed to the GNU General Public License (GPL), as of version 0.12. 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."[18]

GPL version 3

Currently, Linux is licensed only under version 2 of the GPL,[2] with (unlike much other GPL software) no option to use a later version, and there is some controversy over how easily it could be changed to use later GPL versions such as the new version 3 (and whether this is even desirable).[19] Torvalds himself specifically indicated upon the release of version 2.4.0 that his own code is only under version 2.[20] 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.[21] 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."[22]

Loadable kernel modules and firmware

It is debated whether Loadable Kernel Modules (LKMs) should 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. Not all Linux 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'". 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 (ie. 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."[23] Proprietary graphics drivers, in particular, are heavily discussed. Ultimately, it is likely that such questions can only be resolved by a court.

One point of licensing controversy is Linux's use of firmware "binary blobs" to support some hardware devices. Richard Stallman claims that these blobs make Linux partially non-free software, and that distributing Linux may even be violating the GPL (which requires "complete corresponding source code" to be available).[24] In response, the FSFLA started a project, Linux-libre, to create a completely free kernel without proprietary objects, which is used by some completely free distributions.[25][26]


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. Several Linux backers retained legal counsel and filed suit against Della Croce, who agreed in 1998 to assign the trademark to Torvalds.

SCO litigation

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 only 326 lines of code, most of which were uncopyrightable.[27] In August 2007, the court in the Novell case ruled that SCO did not actually own the Unix copyrights to begin with,[28] though the Tenth Circuit Court of Appeals ruled in August 2009 that the question of who owned the copyright properly remained for the jury to answer.[29]

Technical features

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


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. The graphics system most people use with Linux doesn't run in the kernel, in contrast to that found in Microsoft Windows.

Kernel mode preemption allows device drivers to be preempted under certain conditions. This feature was added to handle hardware interrupts correctly and improve support for symmetric multiprocessing (SMP). Preemption also improves latency, increasing responsiveness and making Linux more suitable for real-time applications.

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.

Tanenbaum-Torvalds debate

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

Programming languages

Linux 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 Linux. In 2004, Intel claimed to have modified the kernel so that its C compiler also was capable of compiling it.[34] There was another such reported success in 2009 with a modified 2.6.22.[35][36]

Many other languages are used in some way, primarily in connection with the kernel build process (the methods whereby the bootable image is created from the sources). These include Perl, Python, and various shell scripting languages. Some drivers may also be written in C++, Fortran, or other languages, but this is strongly discouraged. Linux's build system only officially supports GCC as a kernel and driver compiler.


While not originally designed to be portable, Linux is now one of the most widely ported operating system kernels, running on a diverse range of systems from the iPAQ (a handheld computer) to the IBM System z9 (a massive mainframe server that can run hundreds or even thousands of concurrent Linux instances). Linux runs as the main operating system on IBM's Blue Gene supercomputers. As of June 2009, Linux is the OS on more than 88% of systems on the Top 500 supercomputers list.[37] Also, Linux has been ported to various handheld devices such as TuxPhone and Apple's iPod. The Android operating system, developed for mobile phone devices, uses a modified version of the Linux kernel[38][39].

Virtual machine architectures

The Linux kernel has extensive support for and runs on many virtual machine architectures both as the host operating system and as a client operating system. The virtual machines usually emulate Intel x86 family of processors, though in a few cases PowerPC or AMD processors are also emulated.

Estimated cost to redevelop

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) in 2004 prices using the COCOMO man-month estimation model.[40] 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).[41]

This topic was revisited in October 2008 by Amanda McPherson, Brian Proffitt and Ron Hale-Evans. Using David A. Wheelers 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). [42]

Feature history

Version 1.0 of the Linux kernel was released on 14 March 1994.[43] 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[44]) gained support for computer systems using processors based on the Alpha, SPARC, and MIPS architectures.

Version 2.0 was released 9 June 1996.[45] 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[46]) removed the global spinlock and provided improved SMP support, and added support for the m68k and PowerPC architectures as well as new filesystems (including read-only support for Microsoft’s NTFS filesystem).[47]

Version 2.4.0, released on 4 January 2001,[48] contained support for ISA Plug and Play, USB, and PC Cards.[49] 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 filesystems.

Version 2.6.0 was released on 18 December 2003.[50] The 2.6 series of kernels is still the active series of stable kernels as of 1 December 2009. 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 (up from 215), substantially increased the number of device types and the number of devices of each type, improved 64-bit support, support for filesystems of up to 16 terabytes, in-kernel preemption, support for the Native POSIX Thread Library, 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 filesystems 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 of



Template:Timeline Linux Kernel

Development model

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 three months, 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, maybe others).

Most Linux users use 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.

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 elected 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.[52] 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.[53] 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.[54] The stable team picked up on the idea[55] 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.[56] 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.[57][58] 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.


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

Kernel series Current version Maintainer
2.0 2.0.40[59] David Weinehall
2.2 2.2.27-rc2[60] Marc-Christian Petersen (former maintainer Alan Cox)
2.4[61] Willy Tarreau (former maintainer Marcelo Tosatti)
2.6.16[62] Adrian Bunk
2.6.27[63] Greg Kroah-Hartman[55]
2.6.32[64] Greg Kroah-Hartman[65]
2.6.x (current only) (releases every three months) Linus Torvalds
2.6.x-linux-next latest development version

Other Linux kernel programmers who maintain subsystems inside the kernel[66] include:

Revision control

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, a 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.[67] Git soon developed into a separate project in its own right and gained wider adoption in the free software community.

Version numbering

The Linux kernel has had three different numbering schemes.

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.[68] From 0.95 on there were many patch releases between versions.

After the 1.0 release and prior to version 2.6, the version 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 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). The major revision was used 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.

Since 2004, after version 2.6.0 was released, the kernel developers held several discussions regarding the release and version scheme[69][70] and ultimately Linus Torvalds and others decided that a much shorter release cycle would be beneficial. Since then, the version has been composed of three or four numbers. The first two numbers became largely irrelevant, and the third number is the actual version of the kernel. The fourth number accounts for bug and security fixes (only) to the kernel version.

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, 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.

Regular development pre-releases are titled release candidates, which is indicated by appending the suffix 'rc' to the kernel version, followed by an ordinal number.

Also, 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.

See also


  1. InfoWorld. "Linux creator Torvalds still no fan of GPLv3". 
  2. 2.0 2.1 2.2 COPYING
  4. Linus Torvalds (2006-09-25). "Re: GPLv3 Position Statement". 
  5. Marjorie Richardson (1 November 1999). "Interview: Linus Torvalds". Linux Journal. Retrieved 20 August 2009. 
  6. Free as in Freedom by Sam Williams. O'Reilly books, 2002
  7. 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." 
  8. "What would you like to see most in minix?". comp.os.minix. (Web link).
  9. "Free minix-like kernel sources for 386-AT". comp.os.minix. (Web link).
  10. Torvalds, Linus. "Release Notes for Linux v0.12". The Linux Kernel Archives. Retrieved 2007-02-21. 
  11. (19 January 1992). "Troubles with Partitions". comp.os.minix. (Web link). Retrieved on 2007-01-07.
  12. (31 March 1992). "It's here!". comp.os.linux. (Web link). Retrieved on 2007-01-07.
  13. "Linux Kernel Data."
  14. Paul, Ryan (July 2009). "Microsoft aims at VM market with Linux kernel code offering". Retrieved 2009-07-22. 
  15. Holwerda, Thom (July 2009). "Microsoft's Linux Kernel Code Drop Result of GPL Violation". Retrieved 2009-07-23. 
  16. Microsoft (July 2009). "Microsoft Contributes Linux Drivers to Linux Community". Retrieved 2009-07-23. 
  17. Richmond, Gary (August 2009). "Yes Linus, Microsoft hating is a disease. And it's a pandemic". Retrieved 2009-08-01. 
  18. Yamagata, Hiroo (1997). "The Pragmatist of Free Software". HotWired. Retrieved 2007-02-21. 
  19. Corbet, Jonathan (2006-01-31). "GPLv3 and the kernel". Retrieved 2007-02-21. 
  20. 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. 
  21. Cox, Alan (2006-01-20). "Re: GPL V3 and Linux". Linux-kernel mailing list archive. Retrieved 2007-02-21. 
  22. Shankland, Stephen (25 September 2006). "Top Linux programmers pan GPL 3". Retrieved 2007-02-21. 
  23. Re: Linux GPL and binary module exception clause?
  24. Stallman, Richard (2006-10-11). "Linux, GNU, and freedom". Free Software Foundation. Retrieved 2007-02-21. 
  25. "Linux-libre project". Retrieved 2009-10-05. 
  26. "Trisquel GNU/Linux-libre". Retrieved 2009-10-05. 
  27. "Report from the Courthouse 7 March".  Groklaw article
  28. "Court Rules: Novell owns the UNIX and UnixWare copyrights".  Groklaw article
  29. Ryan, Justin (August 2009). "SCO Will Try Again". Retrieved 2009-08-30. 
  30. O'Reilly (1999). "The Tanenbaum-Torvalds Debate". O'Reilly. Retrieved 2006-11-22. 
  31. (29 January 1992). "LINUX is obsolete". comp.os.minix. (Web link). Retrieved on 2006-05-10.
  32. Torvalds, Linus (9 May 2006). "Hybrid kernel, not NT". Retrieved 2007-01-06. 
  33. Tanenbaum, Andy (12 May 2006). "Tanenbaum-Torvalds Debate: Part II". Retrieved 2007-01-06. 
  34. Linux kernel patch for Intel Compiler
  37. "Operating system Family". Top 500 Supercomputer Sites. June 2009. 
  38. 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 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." 
  39. "Linux developer explains Android kernel code removal". ZDNet. 2010-02-02. Retrieved 2010-02-03. 
  40. David A. Wheeler. "Linux Kernel 2.6: It's Worth More!". 
  41. Economic impact of FLOSS on innovation and competitiveness of the EU ICT sector, Table 3 on page 50.
  42. Estimating Total Development Cost Of a Linux Distribution, Table on page 6.
  43. Kernel 1.0 Source Code Release (last checked 2008-10-27)
  44. Kernel 1.2 Source Code Release (last checked 2008-10-27)
  45. Kernel 2.0.x Source Code Releases (last checked 2008-10-27)
  46. Kernel 2.2.x Source Code Releases (last checked 2008-10-27
  47. The Wonderful World of Linux 2.2 (last checked 2008-10-27)
  48. Kernel 2.4.x Source Code Releases (last checked 2008-10-27)
  49. The Wonderful World of Linux 2.4 (last checked 2008-10-27)
  50. Kernel 2.6.x.y Source Code Releases (last checked 2008-10-27)
  55. 55.0 55.1 Greg Kroah-Hartman (2009-09-08). "Re: 2.6.27 maintenance plans after 2.6.32 is released". linux-kernel mailing list. 
  56. 2.6.23-rc6-mm1, "This Just Isn't Working Any More", from KernelTrap
  59. David Weinehall (2004-02-08). "[ANNOUNCE] Linux-kernel 2.0.40 aka ``The Moss-covered Tortoise''". 
  60. Marc-Christian Petersen (2005-01-13). "Linux 2.2.27-rc2". 
  61. Willy Tarreau (2009-07-26). "Linux". linux-kernel mailing list. 
  62. Adrian Bunk (2008-07-21). "Linux". linux-kernel mailing list. 
  63. Greg Kroah-Hartman (2009-09-15). "Linux". linux-kernel mailing list. 
  64. Greg Kroah-Hartman (2010-01-18). "Linux". linux-kernel mailing list. 
  65. Greg Kroah-Hartman (2010-01-18). "Stable kernel tree status, January 18, 2010". linux-kernel mailing list. 
  66. See the Linux MAINTAINERS file.
  67. Linux Kernel Mailing List (2005-06-17). "Linux 2.6.12". 
  68. Linux Kernel Archives - Volume 1 (Riley Williams)

External links

Personal tools

Served in 2.448 secs.