Information AboutLinux Kernel |
| CATEGORIES ABOUT LINUX KERNEL | |
| free system software | |
| linux | |
| monolithic kernels | |
| computing timelines | |
The Linux kernel is a Unix-like Operating System Kernel that was begun by Linus Torvalds in 1991 and subsequently developed with the assistance of developers worldwide. Developed under the GNU General Public License , Linux is Free Software . The kernel is best known for its use in the GNU/Linux Operating System . HISTORY The project was launched in 1991 with a famous post to the Usenet newsgroup comp.os.minix that includes this sentence: "I'm doing a (free) operating system (just a hobby, won't be big and professional like Gnu ) for 386 ( 486 ) AT clones..." {Link without Title} At the time, the GNU project had created many of the components required for a free operating system, but its own kernel project, the 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 Hacker s contributed code and ideas to the Linux kernel, and today it has received contributions from thousands of programmers. Timeline
::''"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 {Link without Title} 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"''
Mascot The Linux mascot is a penguin named Tux , created by Larry Ewing in May 1996 after an initial suggestion made by Alan Cox [http://www.ussg.iu.edu/hypermail/linux/kernel/9605/0237.html and further refined by Linus Torvalds on the Linux Kernel mailing list The mascot is a penguin because as Torvalds put it, "Linus likes penguins. That's it." [http://www.ussg.iu.edu/hypermail/linux/kernel/9605/1203.html The name Tux was suggested to represent (T)orvalds (U)ni(X) [http://www.ussg.iu.edu/hypermail/linux/kernel/9606/0839.html], and it stuck. 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."'' {Link without Title} One general question about the application of the GPL to Linux involves whether loadable kernel modules are considered "derived works" under copyright law, and thereby fall under the terms of the GPL. Torvalds has stated his belief that modules using only a limited, "public" subset of the kernel interfaces can sometimes be non-derived works, thus allowing some binary-only drivers and other modules not obeying the GPL. Not all kernel contributors agree with this interpretation, however, and even Torvalds agrees that many kernel modules are clearly derived works, and indeed he states that ''kernel modules ARE derivative "by default"''. Ultimately, such questions can only be resolved by a court. Currently, the Linux kernel 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) Torvalds himself indicated in version 2.4.0 that his own code is only under version 2 [http://www.uwsg.iu.edu/hypermail/linux/kernel/0009.1/0096.html , but Alan Cox pointed out that very few other kernel contributors have specified a particular version of the GPL [http://lwn.net/Articles/169831/]. (The terms of the GPL state that if no version is specified, then any version may be used.) Linux is a Registered Trademark of Linus Torvalds. 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. 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 the Linux kernel project 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. To date, no proof of SCO's claims of copied code in Linux has been provided and SCO's claims have varied widely. TECHNICAL FEATURES Architecture The Linux kernel includes true Multitasking , Virtual Memory , Shared Libraries , demand loading, shared Copy-on-write executables, proper Memory Management , and TCP/IP Networking . Today Linux is a module-loading Monolithic Kernel . Device Driver s and kernel extensions typically run in Ring 0 , with full access to the hardware, although some run in User Space . 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 . 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 a famous Flame War between Linus Torvalds and Andy Tanenbaum on comp.os.minix in 1992 . [http://www.google.com/groups?threadm=12595%40star.cs.vu.nl The complete source code of various versions of the Linux kernel can be browsed at http://lxr.linux.no . The complete source code of the latest versions of the Linux kernel can be downloaded from http://www.kernel.org . Kernel panic See Also: 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 or overheating/damaged processor.Programming languages The Linux kernel is written in that version of the C Programming Language which is supported by the GNU C Compiler (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 a Linux kernel. Recently, Intel claims to have modified its C compiler so that it also is capable of correctly compiling the kernel. 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 Script ing languages. Some drivers may also be written in C++ , Fortran , or other languages, but this behavior is strongly discouraged. The kernel's build system only officially supports the GCC as a kernel and driver compiler. Portability While not originally intended as a Portable operating system, 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), to the iPod, a portable mp3 player (see below for link). Linux is intended to run as the main operating system on IBM's new Blue Gene Supercomputer architecture when it is finished. Linus included, perhaps humorously, BogoMips into the kernel as a performance pseudo-comparison tool. It is important to note that Linus' efforts were also directed successfully at a different sort of portability. Portability, according to Linus, 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 GPLed and other Open Source applications running. Linux currently runs on the following machine architectures:
A complete list of ports is at Linux Ports . 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 providers of GNU/Linux operating systems 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 {Link without Title} (e.g. 2.2.1, 2.4.13 or 2.6.12.3).
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 slight Fork of the kernel by that person. e.g. ck stands for Con Kolivas , ac stands for Alan Cox , whereas mm stands for Andrew Morton . 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: Other Linux kernel programmers include Robert Love and Ingo Molnar . (See the Linux MAINTAINERS file ). Stable version history
REFERENCES
EXTERNAL LINKS
''The following are to be merged''
Linux 2.6
Pages with links to kernel resources
|
|
|