Jump to content

Linux kernel: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 279: Line 279:
*[http://www.oreilly.com/catalog/understandlk/ Understanding the Linux Kernel, 3rd Edition] (Book)
*[http://www.oreilly.com/catalog/understandlk/ Understanding the Linux Kernel, 3rd Edition] (Book)
*[http://kerneltrap.org/node/1735 Linux: The GPL And Binary Modules]
*[http://kerneltrap.org/node/1735 Linux: The GPL And Binary Modules]
*[http://arc-linux.org/Main_Page ARC Linux].


''The following are to be merged''
''The following are to be merged''

Revision as of 06:22, 23 October 2006

Linux
Developer(s)Linus Torvalds (creator) and others
Stable release
2.6.18.1 / 14 October 2006
Repository
TypeKernel
LicenseGNU General Public License
Websitehttp://www.kernel.org/

The Linux kernel is a Unix-like operating system kernel best known for its use in the GNU/Linux operating system. Released under the GNU General Public License (GPL) and developed by contributors worldwide, Linux is one of the most prominent examples of free software.

History

Linux was created by Linus Torvalds in 1991. 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. This left a space for the Linux kernel to fill, and despite the limited functionality of the early versions it rapidly accumulated developers and users. Early on, Minix hackers contributed code and ideas to the Linux kernel, and today it has received contributions from thousands of programmers.

Timeline

  • April 1991 - Linus Torvalds, then 21 years old, starts working on some simple ideas for an operating system. He starts with a task switcher in 386 assembly and a terminal driver.
  • 25 August 1991 - Torvalds posts to comp.os.minix:

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

  • September 1991 - Linux version 0.01 is released (10,239 lines of code).
  • October 1991 - Linux version 0.02 is released.[2]
  • December 1991 - Linux 0.11 is released. This version is the first that is self-hosted - Linux 0.11 can be compiled under Linux 0.11.
  • January 19 1992 - First post to alt.os.linux newsgroup. [3]
  • March 31 1992 - The newsgroup comp.os.linux is created. [4]
  • March 1992 - Linux version 0.95 is the first to be capable of running the X Window System.
  • During the whole of 1993, and early 1994 - 15 development versions 0.99.
  • March 14 1994 - Linux 1.0.0 is released (176,250 lines of code).
  • March 1995 - Linux 1.2.0 is released (310,950 lines of code).
  • May 9 1996 - Tux the penguin is suggested as mascot for Linux.
  • June 9 1996 - Linux 2.0.0 is released (777,956 lines of code).
  • January 25 1999 - Linux 2.2.0 is released (1,800,847 lines of code).
  • December 18 1999 - IBM mainframe patches for 2.2.13 published, allowing Linux to be used on enterprise-class machines.
  • January 4 2001 - Linux 2.4.0 is released (3,377,902 lines of code).
  • December 17 2003 - Linux 2.6.0 is released (5,929,913 lines of code).
  • April 24 2006 - Linux 2.6.16.11 is released (6,981,110 lines of code).[5]

Pronunciation

In 1992, Torvalds explained how he pronounces the word Linux:

'li' is pronounced with a short [ee] sound: compare prInt, mInImal etc. 'nux' is also short, non-diphthong, like in pUt {IPA /ʊ/}. It's partly due to minix: linux was just my working name for the thing, and as I wrote it to replace minix on my system, the result is what it is... linus' minix became linux.

— Linus Torvalds, comp.os.linux newsgroup[6]

An audio file of Torvalds saying "Hello, this is Linus Torvalds, and I pronounce Linux as Linux" can be found here. Note that in English, "Linux" and "Minix" are usually pronounced with a short i (IPA: /ɪ/) sound that is different from Torvalds' Finland-Swedish pronunciation of these words.

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). This license allows distribution and even sale of possibly modified versions of Linux but requires that all those copies be released under the same license and be accompanied by source code.

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

Firmwares controversy

One point of licensing controversy is the Linux's use of firmware "binary blobs" to support some hardware devices. Richard Stallman claims that these blobs make Linux partially non-free, and that distributing Linux may even be violating the GPL (which requires "complete corresponding source code" to be available).[8]

GPL version 3

Currently, Linux is licensed under version 2 of the GPL, and there is some controversy over how easily it could be changed to use later GPL versions such as the upcoming version 3 (and whether this is desirable).[9] Torvalds himself indicated in version 2.4.0 that his own code is only under version 2.[10] 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.[11]

Loadable Kernel Modules licensing

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 not obeying 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."[12] Especially proprietary graphics drivers are heavily discussed. Ultimately, such questions can only be resolved by a court.

Trademark

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 contributed some portions of SCO's copyrighted Unix source code to Linux in violation of IBM's license to use that Unix source code. 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. 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.

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.

Architecture

Linux is a monolithic kernel. Device drivers and kernel extensions run in kernel space (ring 0), with full access to the hardware, although some exceptions run in user space. The GNU/Linux graphics subsystem (the X Window System) is not part of the kernel, is optional, and runs in user space, in contrast with Microsoft Windows.

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

The fact that Linux is not a microkernel was the topic of the famous Tanenbaum-Torvalds debate.

Unlike traditional monolithic kernels, device drivers are easily configured as modules, and loaded or unloaded while running the system.

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.

Programming languages

Linux is written in that version of the C programming language which is supported by GCC (which has introduced a number of extensions and changes to standard C), together with a number of relatively 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. Recently, Intel claims to have modified its C compiler so that it is also capable of correctly compiling it.[13]

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.

Portability

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 2006, Linux is the OS on 75% of systems on the Top 500 supercomputers list, including the top two on the list. Torvalds included, perhaps humorously, BogoMips into the kernel as a performance pseudo-comparison tool.

It is important to note that Torvalds' efforts were also directed successfully at a different sort of portability. Portability, according to Torvalds, was the ability to easily compile applications from a variety of sources on his system; thus Linux originally became popular in part because it required the least effort to get popular free software and other open source applications running.

Linux supports the following machine architectures:

Versions

Further developing his own code and integrating changes made by other programmers, Linus Torvalds keeps releasing new versions of the Linux kernel. These are called "vanilla" kernels, meaning they have not been modified by anyone. Many Linux operating system vendors modify the kernels of their product, mainly in order to add support for drivers or features which have not officially been released as stable, while some distributions, such as Slackware, rely on vanilla kernels.

Version numbering

The version number of the Linux kernel currently consists of four numbers, following a recent change in the long-standing policy of a three-number versioning scheme. For illustration, let it be assumed that the version number is composed thus: A.B.C[.D] (e.g. 2.2.1, 2.4.13 or 2.6.12.3).

  • The A number denotes the kernel version. It is changed least frequently, and only when major changes in the code and the concept of the kernel occur. It has been changed twice in the history of the kernel: In 1994 (version 1.0) and in 1996 (version 2.0).
  • The B number denotes the major revision of the kernel.
    • Prior to the Linux 2.6.x series, even numbers indicate a stable release, i.e. one that is deemed fit for production use, such as 1.2, 2.4 or 2.6. Odd numbers have historically been development releases, such as 1.1 or 2.5. They were for testing new features and drivers until they became sufficiently stable to be included in a stable release.
    • Starting with the Linux 2.6.x series, there is no significance to even or odd numbers, with new feature development going on in the same kernel series. Linus Torvalds has stated that this will be the model for the foreseeable future.
  • The C number indicates the minor revision of the kernel. In the old three-number versioning scheme, this was changed when security patches, bugfixes, new features or drivers were implemented in the kernel. With the new policy, however, it is only changed when new drivers or features are introduced; minor fixes are handled by the D number.
  • A D number first 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. Bug-fixes and security patches are now managed by the fourth number, whereas bigger changes are only implemented in minor revision changes (the C number).

Also, sometimes after the version there will be some more letters such as 'rc1' or 'mm2'. The 'rc' refers to release candidate and indicates a non-official release. Other letters are usually (but not always) the initials of a person. This indicates a development branch of the kernel by that person. e.g. ck stands for Con Kolivas, ac stands for Alan Cox, whereas mm stands for Andrew Morton.

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. 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 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 "stable" branch. This had the desirable effect of not having to maintain an old stable branch, making new features quickly available, and getting more testing of the latest code.

However, the new 2.6 development model also meant that there were no stable branch for people just wanting security and bug fixes, and not needing the latest features. Fixes were only put into the latest version, so if you wanted a version with all known bugs fixed you would also get all the latest little tested code, and risked that things which had previously worked suddenly broke. A partial fix for this was the previously mentioned fourth version number digit (y in 2.6.x.y), which are series of point releases created by the stable team (Greg Kroah-Hartman, Chris Wright, maybe others). The stable team only released updates for the most recent kernel however, so this did not solve the problem of the missing stable kernel series. Linux distribution vendors, such as Red Hat and Debian, maintain the kernels which ship with their releases, so a solution for some people is to just follow a vendor kernel.

As a response to the lack of a stable kernel tree where people could coordinate the collection of bugfixes, in December of 2005 Adrian Bunk announced that he would keep releasing 2.6.16.y kernels when the stable team moved on to 2.6.17 [1]. He also plans to include driver updates, making the maintainance of the 2.6.16 series very similar to the old rules for maintainance of a stable series such as 2.4 [2].

Maintenance

While Linus Torvalds supervises code changes and releases to the latest kernel versions, he has delegated the maintenance of older versions to other programmers:

Kernel series Maintainer
2.4 Willy Tarreau (former maintainer Marcelo Tosatti)
2.6.16 Adrian Bunk
2.6 Andrew Morton / Linus Torvalds

Other Linux kernel programmers include Robert Love and Ingo Molnar. (See the Linux MAINTAINERS file).

Stable version history

  • Version 1.0 of March 1994 supported only single-processor i386 machines.
  • Version 1.2 of March 1995 added support for Alpha, Sparc and MIPS.
  • Version 2.0 of June 1996 added support for more processors and included SMP support.
  • Version 2.2 of January 1999 (The Wonderful World of Linux 2.2).

References

  • Torvalds, Linus (2001). Just for Fun: The Story of an Accidental Revolutionary. HarperBusiness. ISBN 0-06-662072-4 (hardcover); HarperAudio ISBN 0-694-52539-1. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help) (audio tape, abridged ed., read by David Diamond) - on the beginnings of the Linux kernel
  • [3], Nikolai Bezroukov. Portraits of Open Source Pioneers. Ch 4: A benevolent dictator (Softpanorama e-book).
  • "LinkSys and binary modules". LWN.net Weekly Edition. October 16 2003. {{cite web}}: Check date values in: |date= (help)
  • FreeBSD/Linux kernel source code cross-reference. Browsable Linux (and other operating system) kernel source cross-reference.
  • Kernel Cross-Reference (browsable Linux kernel source)
  • KernelHQ - a browsable kernel source tree - with all versions present, and with browsable diffs

See Also

  • menuconfig — a tool for configuring Linux prior to building it from source
  • Revolution OS — a documentary on the history of Linux featuring several interviews with prominent hackers, including Torvalds

The following are to be merged

Linux 2.6