document_title: Linux kernel

question_text: who is the current maintainer of the linux kernel

question_tokens: who is the current maintainer of the linux kernel

text: Linux kernel

text: History[edit]

text: In April 1991, Linus Torvalds, at the time a 21-year-old computer science 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:[18]

text: 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).

text: 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 :-(.

text: [...] 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.

text: 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 gained developers and users.

text: By September 1991, version 0.01 of the Linux kernel 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, version 0.02 of the Linux kernel was released.[19]

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

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

text: 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.

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

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

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

tag: ul

text: 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.

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

text: Version 3.10 of the Linux kernel, released in June 2013, contains 15,803,499 lines of code,[26] while the version 4.1, released in June 2015, has grown to over 19.5 million lines of code contributed by almost 14,000 programmers.[27]

text: Tanenbaum–Torvalds debate[edit]

text: 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.[28] The debate, started in 1992 on the Usenet discussion group comp.os.minix, was about Linux and kernel architecture in general.[29] 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,[30] and on 12 May 2006 Tanenbaum wrote a position statement.[31]

text: Popularity[edit]

text: The huge rise in popularity of the Android operating system, which includes the Linux kernel, has made the kernel the most popular choice for mobile devices, rivaling the installed base of all other operating systems.[32][33][34] Including previous years, three billion Android smartphones were estimated to have been sold by the end of 2014.

text: Many consumer routers also use the Linux kernel,[35] as well as a wide variety of other embedded devices, such as smart TVs, set-top boxes, and webcams. Many desktop Linux distributions including the Linux kernel exist, but the usage share of Linux distributions is low in comparison to other operating systems.

text: Legal aspects[edit]

text: Licensing terms[edit]

text: Initially, Torvalds released Linux under a license which forbade any commercial use.[36] This was changed in version 0.12 by a switch to the GNU General Public License (GPL).[20] 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.

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

text: GPL version 3[edit]

text: The Linux kernel is licensed explicitly only under version 2 of the GPL,[6] without offering the licensee the option to choose "any later version", which is a common GPL extension. There was considerable debate about how easily the license could be changed to use later GPL versions (including version 3), and whether this change is even desirable.[37] Torvalds himself specifically indicated upon the release of version 2.4.0 that his own code is released only under version 2.[38] However, the terms of the GPL state that if no version is specified, then any version may be used,[verification needed] and Alan Cox pointed out that very few other Linux contributors had specified a particular version of the GPL.[39]

text: In September 2006, a survey of 29 key kernel programmers indicated that 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."[40] This group of high-profile kernel developers, including Linus Torvalds, Greg Kroah-Hartman and Andrew Morton, commented on mass media about their objections to the GPLv3.[41] They referred to clauses regarding DRM/tivoization, patents, "additional restrictions" and warned a Balkanisation of the "Open Source Universe" by the GPLv3.[41][42] Linus Torvalds, who decided not to adopt the GPLv3 for the Linux kernel, reiterated his criticism even years later.[43]

text: Loadable kernel modules[edit]

text: 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.

text: 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.[44] 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.[45] 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'".[46]

text: 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."[47] Proprietary graphics drivers, in particular, are heavily discussed. Ultimately, it is likely that such questions can only be resolved by a court.

text: Firmware binary blobs[edit]

text: One point of licensing controversy is the use of firmware "binary blobs" in Linux kernel to support several hardware devices. These files are under a variety of licenses, out of which many are restrictive and their exact underlying source code is usually unknown.[8]

text: In 2002, Richard Stallman stated why, in his point of view, such blobs make the Linux kernel partially non-free software, and that distributing Linux kernel "violates the GPL", which requires "complete corresponding source code" to be available.[7] In 2008, Free Software Foundation Latin America started Linux-libre as a project that creates a completely free variant of the Linux kernel without proprietary objects; it is used by certain completely free Linux distributions, such as those endorsed by the Free Software Foundation, while it can also be used on most distributions.[48]

text: On 15 December 2010, the Debian Project announced that the next Debian stable version "6.0 Squeeze" would come with a kernel "stripped of all non-free firmware bits".[49] This policy was continued to be applied in later stable Debian releases.

text: Trademark[edit]

text: 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.[50] 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.[51][52]

text: SCO litigation[edit]

text: 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.

text: 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.[53] In August 2007, the court in the Novell case ruled that SCO did not actually own the Unix copyrights to begin with,[54] 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.[55] The jury case was decided on 30 March 2010 in Novell's favour.[56]

text: Architecture[edit]

text: The Linux kernel is a monolithic kernel, supporting true preemptive multitasking (both in user mode and, since the 2.6 series, in kernel mode[57][58]), virtual memory, shared libraries, demand loading, shared copy-on-write executables (via KSM), memory management, the Internet protocol suite, and threading.

text: 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/CUSE, and parts of UIO.[59][60] The graphics system most people use with Linux does not run within the kernel. Unlike standard monolithic kernels, device drivers are easily configured as modules, and loaded or unloaded while the system is running. Also, unlike standard monolithic kernels, device drivers can be pre-empted under certain conditions; this feature was added to handle hardware interrupts correctly, and to better support symmetric multiprocessing.[58] By choice, the Linux kernel has no binary kernel interface.[61]

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

text:
Various layers within Linux, also showing separation between the userland and kernel space

User mode
User applications
For example, bash, LibreOffice, GIMP, Blender, 0 A.D., Mozilla Firefox, etc.

Low-level system components:
System daemons:
systemd, runit, logind, networkd, PulseAudio, ...
Windowing system:
X11, Wayland, Mir, SurfaceFlinger (Android)
Other libraries:
GTK+, Qt, EFL, SDL, SFML, FLTK, GNUstep, etc.
Graphics:
Mesa, 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

Other components: 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.)

text: Programming language[edit]

text: 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.

text: Compiler compatibility[edit]

text: GCC is the default compiler for the Linux kernel source. In 2004, Intel claimed to have modified the kernel so that its C compiler was also capable of compiling it.[63] There was another such reported success in 2009, with a modified 2.6.22 version of the kernel.[64][65]

text: Since 2010, effort has been underway to build the Linux kernel with Clang, an alternative compiler for the C language;[66] as of 12 April 2014, the official kernel could almost be compiled by Clang.[67][68] The project dedicated to this effort is named LLVMLinux after the LLVM compiler infrastructure upon which Clang is built.[69] LLVMLinux does not aim to fork either the Linux kernel or the LLVM, therefore it is a meta-project composed of patches that are eventually submitted to the upstream projects. By enabling the Linux kernel to be compiled by Clang that, among other advantages, is known for faster compilation compared with GCC, kernel developers may benefit from a faster workflow due to shorter compilation times.[70]

text: Interfaces[edit]

text: This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (January 2015) (Learn how and when to remove this template message)

text: Conformance to standards is a general policy for the Linux kernel's internals. Another rule is that a kernel component is not accepted into the Linux kernel mainline if there is only proprietary user-space software using that component.[citation needed]

text: Kernel-to-userspace API[edit]

text: 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. Inspur K-UX is distribution by chinese Inspur based on Red Hat Enterprise Linux and is a certified "UNIX" by The Open Group.[72]

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

text: Kernel-to-userspace ABI[edit]

text: 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).

text: In-kernel API[edit]

text: 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, others have not. There are no guarantees regarding the in-kernel APIs. Maintainers and contributors are free to augment or change them at any time.[73]

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

text:
Video4Linux –  for video capture hardware
Advanced Linux Sound Architecture (ALSA) –  for sound cards
New API –  for network interface controllers
Direct Rendering Manager –  for graphics accelerators
KMS driver –  for display controllers
mac80211 –  for wireless network interface controllers[74]
WEXT –  for wireless network interface controllers (obsolete).

text: In-kernel ABI[edit]

text: Some organizations have strongly supported defining and maintaining of a stable in-kernel ABI over several releases.[citation needed] For example, it would benefit hardware manufacturers which release proprietary kernel modules and distribute binary-only software (e.g. device drivers).[citation needed] However, the Linux kernel developers choose not to maintain a stable in-kernel ABI.[75] This allows Linux kernel development to happen much more quickly.[citation needed]

text: Technical features[edit]

text: Preemption[edit]

text: 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.[77] Toward 2.6 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.[78]

text: The Linux kernel contains different scheduler classes.[79] By default the kernel uses a scheduler mechanism called the Completely Fair Scheduler introduced in the 2.6.23 version of the kernel.[80] Internally this default-scheduler class is also known as SCHED_OTHER, but the kernel also contains two POSIX-compliant[81] 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.[79]

text: Through the use of the real-time Linux kernel patch PREEMPT_RT, support for full preemption of critical sections, interrupt handlers, and "interrupt disable" code sequences can be supported.[82] Partial mainline integration of the real-time Linux kernel patch already brought some functionality to the kernel mainline.[83] 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, which was finally removed by Arnd Bergmann in 2011.[84]

text: Additional scheduling policy known as SCHED_DEADLINE, implementing the earliest deadline first algorithm (EDF), was added in kernel version 3.14, released on 30 March 2014.[85][86]

text: Portability[edit]

text: While not originally designed to be portable,[18][87] 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 performed on the Motorola 68000 platform by Amiga users, who accomplished this by replacing major parts of the kernel. The modifications to the kernel were so fundamental that Torvalds viewed the Motorola version as a fork and a "Linux-like operating system"[87] rather than as an actual port. It was, however, the impetus that Torvalds needed to lead a major restructure of the kernel code to facilitate porting to competing computing architectures. The first Linux endorsed port was to the DEC Alpha AXP 32 bit platform which was demonstrated at DECUS in May, 1995m[88] supporting both 386 and Alpha in a single source tree.[87] DEC was responsible for supplying the hardware necessary to Torvalds to enable a port of Linux to 64 bits[89] that same year.

text: Linux runs as the main operating system on IBM's Blue Gene and other fastest supercomputers, including the top Chinese one. As of June 2017[update], 99+% of the world's 500 fastest supercomputers run some variant of Linux,[10] that is all of them except the 493rd and 494th fastest which run on Unix.[90] Linux has also been ported to various handheld devices such as Apple's iPod and iPhone.[91] Some operating systems developed for mobile phones use modified versions of the Linux kernel, including Google Android, Firefox OS, HP webOS, Nokia Maemo and Jolla Sailfish OS.[92][93][94]

text: Kernel panic and oopses[edit]

text: 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.

text: A report of a non-fatal bug in the kernel is called an "oops"; such deviations from correct behavior of the Linux kernel may allow continued operation with compromised reliability.[95] These crash reports are automatically collected and can be sent upstream by various software, such as kerneloops,[96] ABRT (Fedora)[97] and apport (Ubuntu). KernelOops.org collects these reports and publishes statistics on their website.[98]

text: The kernel panic message might not be printed visibly in some conditions, such as when using a graphical desktop. To debug such conditions, other methods such as attaching a serial port console can be used.

text: Live patching[edit]

text: Rebootless updates can even be applied to the kernel by using live patching technologies such as Ksplice, kpatch and kGraft. Minimalistic foundations for live kernel patching were merged into the Linux kernel mainline in kernel version 4.0, which was released on 12 April 2015. Those foundations, known as livepatch and based primarily on the kernel's ftrace functionality, form a common core capable of supporting hot patching by both kGraft and kpatch, by providing an application programming interface (API) for kernel modules that contain hot patches and an application binary interface (ABI) for the userspace management utilities. However, the common core included into Linux kernel 4.0 supports only the x86 architecture and does not provide any mechanisms for ensuring function-level consistency while the hot patches are applied. As of April 2015[update], there is ongoing work on porting kpatch and kGraft to the common live patching core provided by the Linux kernel mainline.[99][100][101]

text: Security[edit]

text: Computer security is a much-publicized topic in relation to the Linux kernel because a large portion of the kernel bugs present potential security flaws. For example, they may allow for privilege escalation or create denial-of-service attack vectors. Over the years, numerous such flaws were found and fixed in the Linux kernel.[102] New security features are frequently implemented to improve the Linux kernel's security.[103][104]

text: Critics have accused kernel developers of covering up security flaws or at least not announcing them; in 2008, Linus Torvalds responded to this with the following:[105][106]

text: 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.

text: Linux distributions typically release security updates to fix vulnerabilities in the Linux kernel. Many offer long-term support releases that receive security updates for a certain Linux kernel version for an extended period of time.

text: Feature history[edit]

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

text: Version 2.0 was released on 9 June 1996.[109] 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.

text: Version 2.2, released on 20 January 1999,[110] removed the global spinlock and provided improved SMP support, added support for the m68k and PowerPC architectures, and added new file systems (including read-only support for Microsoft's NTFS).[111]

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

text: Version 2.6.0 was released on 17 December 2003.[114] 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 Advanced Linux Sound Architecture (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),[115] 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 of kernel.org.[116]

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

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

text: Version 3.11, released on 2 September 2013,[121] 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).[122]

text: There were no meaningful technical reasons for the numbering change from 2.6.39 to 3.0, or from 3.19 to 4.0. The major version number was increased just to avoid large minor numbers.[23][123]

text: Development[edit]

text: Developer community[edit]

text:
As of 2007, the development of the kernel had shifted from the top 20 most active developers writing 80% of the code to the top 30 writing 30% of the code, with top developers spending more time reviewing changes.[124] Developers can also be categorized by affiliation; in 2007, the top category was unknown while the top corporation was Red Hat with 12% of contributions, and known amateurs at 3.9%.[124] The kernel changes made in year 2007 have been submitted by over 1900 developers, which may be a significant underestimate because developers working in teams usually count as one.[citation needed] It is generally assumed that the community of Linux kernel developers comprises 5000 or 6000 members.
Update from the 2016 Linux Kernel Development Report, issued by the Linux Foundation, covering the period from 3.18 (December 2014) to 4.7 (July 2016): About 1500 developers are contributing to each release from about 200-250 companies on average per release. The top 30 developers contributed a little more than 16% of the code. As of companies, the top contributors are Intel (12.9%) and Red Hat (8.0%), the third and fourth places are held by the 'none' (7.7%) and 'unknown' (6.8%) categories.

text: Codebase[edit]

text: As of 2013[update], the 3.10 release of the Linux kernel had 15,803,499 lines of code. As of 2007, roughly 5% of the code is part of the "core" while 52% is drivers.[124]

text: 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...

text: Linux is evolution, not intelligent design!

text: By this statement it is meant that evolution often does odd (and "sub-optimal") things exactly because it does incremental changes which 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.

text: The conceptual architecture of the Linux kernel has proved its success, while 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 many independent volunteer developers, which suggested that the system portions that require the most development—hardware device drivers, file systems 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.

text: 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.

text: Estimated cost to redevelop[edit]

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

text: 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.3bn (part of a total $10.8bn to redevelop Fedora 9).[130] Again, Garcia-Garcia and Alonso de Magdaleno from University of Oviedo (Spain) estimate that the value annually added to kernel was about €100M between 2005 and 2007 and €225M in 2008, it would cost also more than €1bn (about $1.4bn as of February 2010) to develop in the European Union.[131]

text: As of 7 March 2011[update], using then-current LOC (lines of code) of a 2.6.x Linux kernel and wage numbers with David A. Wheeler's calculations it would cost approximately $3bn (about €2.2bn) to redevelop the Linux kernel as it keeps getting bigger.[132]

text: Development model[edit]

text: This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (March 2011) (Learn how and when to remove this template message)

text: 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.

text: As of 2015[update], in the current development scheme, the main branch of development is not a traditional "stable" branch; instead, it incorporates all kinds of changes, including both the latest features, and 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).

text: The development model for the 2.6 kernel series was significantly different compared to the 2.5 series. Before the 2.6 series, 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 kernel series, some maintainers elected to try backporting of their changes to the stable kernel series, which resulted in bugs being introduced into the 2.4 kernel series. 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.

text: 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.[133][134] 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.[135] 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.[136] The stable team picked up on the idea and as of 2010[update] they continue to maintain that version and release bug fixes for it, in addition to others.[137]

text: 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.[138] 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.[139][140] 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.

text: As of January 2014[update], the in-development version of the Linux kernel is held in an unstable branch named linux-next.[141]

text: Relation with Linux distributions[edit]

text: Most Linux users run a kernel supplied by their Linux distribution. Some distributions ship the "vanilla" 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 usually 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.

text: Maintenance[edit]

text: While Linus Torvalds supervises code changes and releases to the latest kernel versions, he has delegated the maintenance of older versions to other programmers.[142] 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.

text: Releases before 2.6.0[edit]

text:
Version
Original release date
Current version
Maintainer
[show]Support model

Old version, no longer supported: 0.01
000000001991-09-17-000017 September 1991
0.03
Linus Torvalds
EOL

Old version, no longer supported: 0.10
000000001991-11-01-0000November 1991
0.12
Linus Torvalds
EOL

Old version, no longer supported: 0.95
000000001992-03-08-00008 March 1992
0.99.15
Linus Torvalds
EOL

Old version, no longer supported: 1.0
000000001994-03-14-000014 March 1994
1.0.9
Linus Torvalds
EOL

Old version, no longer supported: 1.1
000000001994-04-06-00006 April 1994
1.1.95
Linus Torvalds
EOL

Old version, no longer supported: 1.2
000000001995-03-07-00007 March 1995
1.2.13
Linus Torvalds
EOL

Old version, no longer supported: 1.3
000000001995-06-12-000012 June 1995
1.3.100[143]
Linus Torvalds
EOL

Old version, no longer supported: pre2.0
000000001996-05-12-000012 May 1996
pre2.0.14
Linus Torvalds
EOL

Old version, no longer supported: 2.0
000000001996-06-09-00009 June 1996[109]
2.0.40[144]
David Weinehall
EOL (officially made obsolete with the kernel 2.2.0 release)[145]

Old version, no longer supported: 2.2
000000001999-01-26-000026 January 1999[110]
2.2.26[146]
Marc-Christian Petersen (formerly Alan Cox)
EOL (unofficially obsolete with the 2.2.27-rc2)[147][148]

Old version, no longer supported: 2.4
000000002001-01-04-00004 January 2001[112]
2.4.37.11[149]
Willy Tarreau (formerly Marcelo Tosatti)
EOL (maintained from December 2008 to December 2011), last stable release of the 2.4 kernel series.[149]

Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

text: 2.6.x.y releases[edit]

text: Versions 2.6.16 and 2.6.27 of the Linux kernel were unofficially supported in a long-term support (LTS) fashion,[150] before a 2011 working group in the Linux Foundation started a formal long-term support initiative.[151][152]

text:
Version
Original release date
Current version
Maintainer
[show]Support model

Old version, no longer supported: 2.6
000000002003-12-17-000017 December 2003[114]
2.6.10[153]
Linus Torvalds
EOL (maintained from December 2003 to December 2004)[153]

Old version, no longer supported: 2.6.11
000000002005-03-02-00002 March 2005[154]
2.6.11.12[155]
Greg Kroah-Hartman
EOL (maintained from March 2005 to June 2005)[155]

Old version, no longer supported: 2.6.12
000000002005-06-18-000018 June 2005[156]
2.6.12.6[157]
Greg Kroah-Hartman
EOL (maintained from June 2005 to August 2005)[157]

Old version, no longer supported: 2.6.13
000000002005-08-28-000028 August 2005[158]
2.6.13.5[159]
Greg Kroah-Hartman
EOL (maintained from August 2005 to December 2005)[159]

Old version, no longer supported: 2.6.14
000000002005-10-27-000027 October 2005[160]
2.6.14.7[161]
Greg Kroah-Hartman
EOL (maintained from October 2005 to January 2006)[161]

Old version, no longer supported: 2.6.15
000000002006-01-02-00002 January 2006[162]
2.6.15.7[163]
Greg Kroah-Hartman
EOL (maintained from January 2006 to May 2006)[163]

Old version, no longer supported: 2.6.16
000000002006-03-20-000020 March 2006[164]
2.6.16.62[165]
Adrian Bunk[166] (formerly Greg Kroah-Hartman)[167]
EOL (first LTS release, maintained from March 2006 to July 2008)[134][165]

Old version, no longer supported: 2.6.17
000000002006-06-17-000017 June 2006[168]
2.6.17.14[169]
Greg Kroah-Hartman
EOL (maintained from September 2006 to October 2006)[169]

Old version, no longer supported: 2.6.18
000000002006-09-20-000020 September 2006[170]
2.6.18.8[171]
Greg Kroah-Hartman
EOL (maintained from September 2006 to February 2007)[171]

Old version, no longer supported: 2.6.19
000000002006-11-26-000026 November 2006[172]
2.6.19.7[173]
Greg Kroah-Hartman
EOL (maintained from November 2006 to March 2007)[173]

Old version, no longer supported: 2.6.20
000000002007-02-04-00004 February 2007[174]
2.6.20.21[175]
Greg Kroah-Hartman
EOL (maintained from February 2007 to October 2007)[175]

Old version, no longer supported: 2.6.21
000000002007-04-25-000025 April 2007[176]
2.6.21.7[177]
Greg Kroah-Hartman
EOL (maintained from April 2007 to August 2007)[177]

Old version, no longer supported: 2.6.22
000000002007-07-08-00008 July 2007[178]
2.6.22.19[179]
Greg Kroah-Hartman
EOL (maintained from July 2007 to February 2008)[179]

Old version, no longer supported: 2.6.23
000000002007-10-09-00009 October 2007[180]
2.6.23.17[181]
Greg Kroah-Hartman
EOL (maintained from October 2007 to February 2008)[181]

Old version, no longer supported: 2.6.24
000000002008-01-24-000024 January 2008[182]
2.6.24.7[183]
Greg Kroah-Hartman
EOL (maintained from January 2008 to May 2008)[183]

Old version, no longer supported: 2.6.25
000000002008-04-16-000016 April 2008[184]
2.6.25.20[185]
Greg Kroah-Hartman
EOL (maintained from April 2008 to November 2008)[185]

Old version, no longer supported: 2.6.26
000000002008-07-13-000013 July 2008[186]
2.6.26.8[187]
Greg Kroah-Hartman
EOL (maintained from July 2008 to November 2008)[187]

Old version, no longer supported: 2.6.27
000000002008-10-09-00009 October 2008[188]
2.6.27.62[189]
Willy Tarreau[190] (formerly Adrian Bunk,[191] and formerly Greg Kroah-Hartman)
EOL (second LTS release, maintained from October 2008 to March 2012)[191]

Old version, no longer supported: 2.6.28
000000002008-12-24-000024 December 2008[192]
2.6.28.10[193]
Greg Kroah-Hartman
EOL (maintained from December 2008 to May 2009)[193]

Old version, no longer supported: 2.6.29
000000002009-03-23-000023 March 2009[194]
2.6.29.6[195]
Greg Kroah-Hartman
EOL (maintained from March 2009 to July 2009)[195]

Old version, no longer supported: 2.6.30
000000002009-06-09-00009 June 2009[196]
2.6.30.9[197]
Greg Kroah-Hartman
EOL (maintained from June 2009 to October 2009)[197]

Old version, no longer supported: 2.6.31
000000002009-09-09-00009 September 2009[198]
2.6.31.14[199]
Greg Kroah-Hartman
EOL (maintained from September 2009 to July 2010)[199]

Old version, no longer supported: 2.6.32
000000002009-12-02-00002 December 2009[200]
2.6.32.71[201]
Willy Tarreau[202][203] (formerly Greg Kroah-Hartman)[167][204]
EOL (third LTS release, maintained from December 2009 to March 2016,[202] used in Debian 6 Squeeze.[205] Canonical also provided support until April 2015.[206]

Old version, no longer supported: 2.6.33
000000002010-02-24-000024 February 2010[207]
2.6.33.20[208]
Greg Kroah-Hartman[209]
EOL (fourth LTS release, maintained from March 2011 to November 2011). It was the base for real-time-tree, replaced by 3.0.x.[208][209]

Old version, no longer supported: 2.6.34
000000002010-05-16-000016 May 2010[210]
2.6.34.15[211]
Paul Gortmaker[212]
EOL (fifth LTS release, maintained from January 2011 to February 2014)[211][212]

Old version, no longer supported: 2.6.35
000000002010-08-01-00001 August 2010[213]
2.6.35.14[214]
Andi Kleen[215]
EOL (sixth LTS release, maintained from December 2010 to March 2012)[215]

Old version, no longer supported: 2.6.36
000000002010-10-20-000020 October 2010[216]
2.6.36.4[217]
Greg Kroah-Hartman
EOL (maintained from October 2010 to February 2011)[217]

Old version, no longer supported: 2.6.37
000000002011-01-04-00004 January 2011[218]
2.6.37.6[219]
Greg Kroah-Hartman
EOL (maintained from January 2011 to March 2011)[219]

Old version, no longer supported: 2.6.38
000000002011-03-14-000014 March 2011[220]
2.6.38.8[221]
Greg Kroah-Hartman
EOL (maintained from March 2011 to June 2011)[221]

Old version, no longer supported: 2.6.39
000000002011-05-18-000018 May 2011[222]
2.6.39.4[223]
Greg Kroah-Hartman
EOL (maintained from May 2011 to August 2011), last stable release of the 2.6 kernel series.[223]

Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

text: 3.x.y releases[edit]

text:
Version[a]
Original release date
Current version
Maintainer
[show]Support model

Old version, no longer supported: 3.0
000000002011-07-21-000021 July 2011[23]
3.0.101[224]
Greg Kroah-Hartman[225]
EOL (seventh LTS release, maintained from July 2011 to October 2013, providing the base for real-time tree)[224][225]

Old version, no longer supported: 3.1
000000002011-10-24-000024 October 2011[226]
3.1.10[227]
Greg Kroah-Hartman
EOL (maintained from October 2011 to January 2012)[227]

Older version, yet still supported: 3.2
000000002012-01-04-00004 January 2012[228]
3.2.92[229]
Ben Hutchings[202][230]
Eighth LTS release, maintained from March 2012 to May 2018, used in Ubuntu 12.04 LTS, Debian 7 "Wheezy" and Slackware 14.0.[202][230] Canonical will provide extended support until April 2017.[206]

Old version, no longer supported: 3.3
000000002012-03-18-000018 March 2012[231]
3.3.8[232]
Greg Kroah-Hartman
EOL (maintained from March 2012 to June 2012)[232]

Old version, no longer supported: 3.4
000000002012-05-20-000020 May 2012[233][234]
3.4.113[235]
Li Zefan[202][236] (formerly Greg Kroah-Hartman)
EOL (Ninth LTS release, maintained from May 2012 to October 2016).[237] kernel.org still lists 3.4 as "longterm" but has "Projected EOL" in the past.[202][238]

Old version, no longer supported: 3.5
000000002012-07-21-000021 July 2012[239]
3.5.7[240]
Greg Kroah-Hartman
EOL (maintained from July 2012 to October 2012);[240] Canonical provided extended support until April 2014.[206][241]

Old version, no longer supported: 3.6
000000002012-09-30-000030 September 2012[242]
3.6.11[243]
Greg Kroah-Hartman
EOL (maintained from October 2012 to December 2012)[243]

Old version, no longer supported: 3.7
000000002012-12-10-000010 December 2012[244]
3.7.10[245]
Greg Kroah-Hartman
EOL (maintained from December 2012 to March 2013)[245][246]

Old version, no longer supported: 3.8
000000002013-02-18-000018 February 2013[247]
3.8.13[248]
Greg Kroah-Hartman
EOL (maintained from February 2013 to May 2013);[248] Canonical provided extended support until August 2014.[206][249]

Old version, no longer supported: 3.9
000000002013-04-28-000028 April 2013[250]
3.9.11[251]
Greg Kroah-Hartman
EOL (maintained from April 2013 to July 2013)[251]

Older version, yet still supported: 3.10
000000002013-06-30-000030 June 2013[252]
3.10.107[253]
Willy Tarreau[202][254] (formerly Greg Kroah-Hartman)
Tenth LTS release, maintained from August 2013 to October 2017.[202][255]

Old version, no longer supported: 3.11
000000002013-09-02-00002 September 2013[121]
3.11.10[256]
Greg Kroah-Hartman
EOL (maintained from September 2013 to November 2013);[256] Canonical provided extended support until August 2014.[206] The codename chosen for version 3.11 is "Linux for Workgroups".

Old version, no longer supported: 3.12
000000002013-11-03-00003 November 2013[257]
3.12.74[258]
Jiří Slabý[202][259] (formerly Greg Kroah-Hartman)
EOL (eleventh LTS release, maintained from November 2013 to May 2017.)[259][258]

Old version, no longer supported: 3.13
000000002014-01-19-000019 January 2014[260]
3.13.11[261]
Greg Kroah-Hartman
EOL (maintained from January 2014 to April 2014);[261] Canonical provided extended support until April 2016.[206][262]

Old version, no longer supported: 3.14
000000002014-03-30-000030 March 2014[263]
3.14.79[264]
Greg Kroah-Hartman[202]
EOL (twelfth LTS release, maintained from March 2014 to August 2016)[264]

Old version, no longer supported: 3.15
000000002014-06-08-00008 June 2014[265]
3.15.10[266]
Greg Kroah-Hartman
EOL (maintained from June 2014 to August 2014)[266]

Older version, yet still supported: 3.16
000000002014-08-03-00003 August 2014[267]
3.16.47[268]
Ben Hutchings[202][269] (formerly Greg Kroah-Hartman)
Sixteenth LTS release, maintained from August 2014 to October 2014, May 2016 to April 2020.[202][270] Used in Debian 8 "Jessie".[271] Canonical provided extended support until April 2016.[206][272]

Old version, no longer supported: 3.17
000000002014-10-05-00005 October 2014[273]
3.17.8[274]
Greg Kroah-Hartman
EOL (maintained from October 2014 to January 2015)[274]

Older version, yet still supported: 3.18
000000002014-12-07-00007 December 2014[275]
3.18.71[276]
Greg Kroah-Hartman[277] (formerly Sasha Levin[278]) (formerly Greg Kroah-Hartman)
EOL (thirteenth LTS release, maintained from December 2014 to January 2017)[279] However Greg stated that he will release irregular updates to the 3.18 tree[280]

Old version, no longer supported: 3.19
000000002015-02-08-00008 February 2015[281]
3.19.8[282]
Greg Kroah-Hartman
EOL (maintained from February 2015 to May 2015);[282] last stable release of the 3.x.y kernel series;[283] Canonical provided extended support until July 2016.[206][284]

Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

text: 4.x.y releases[edit]

text:
Version[a][b]
Original release date
Current version
Maintainer
[show]Support model

Old version, no longer supported: 4.0
000000002015-04-12-000012 April 2015[123]
4.0.9[286]
Greg Kroah-Hartman
EOL (maintained from April 2015 to July 2015)[287]

Older version, yet still supported: 4.1
000000002015-06-22-000022 June 2015[288]
4.1.43[289]
Sasha Levin[202][290] (formerly Greg Kroah-Hartman)[291]
Fourteenth LTS release, maintained from July 2015 to September 2017.[202][288]

Old version, no longer supported: 4.2
000000002015-08-30-000030 August 2015[292]
4.2.8[293]
Greg Kroah-Hartman
EOL (maintained from August 2015 to December 2015);[293] Canonical provided extended support until July 2016.[206][294]

Old version, no longer supported: 4.3
000000002015-11-01-00001 November 2015[295]
4.3.6[296]
Greg Kroah-Hartman
EOL (maintained from November 2015 to February 2016)[297]

Older version, yet still supported: 4.4
000000002016-01-10-000010 January 2016[298]
4.4.88[299]
Greg Kroah-Hartman[202]
Fifteenth LTS release, maintained from January 2016 to February 2018.[202][300] Canonical provided extended support until April 2021.[301]

Old version, no longer supported: 4.5
000000002016-03-13-000013 March 2016[302]
4.5.7[303]
Greg Kroah-Hartman
EOL (maintained from March 2016 to June 2016)[304]

Old version, no longer supported: 4.6
000000002016-05-15-000015 May 2016[305]
4.6.7[306]
Greg Kroah-Hartman
EOL (maintained from May 2016 to August 2016)[306]

Old version, no longer supported: 4.7
000000002016-07-24-000024 July 2016[307]
4.7.10[308]
Greg Kroah-Hartman
EOL (maintained from July 2016 to October 2016)[308]

Old version, no longer supported: 4.8
000000002016-09-25-000025 September 2016[309]
4.8.17[310]
Greg Kroah-Hartman
EOL (maintained from September 2016 to January 2017)[310]

Older version, yet still supported: 4.9
000000002016-12-11-000011 December 2016[311]
4.9.50[312]
Greg Kroah-Hartman[202]
Seventeenth LTS release, maintained from December 2016 to January 2019.[202][313] Used in Debian 9 "Stretch".[314]

Old version, no longer supported: 4.10
000000002017-02-19-000019 February 2017[315]
4.10.17[316]
Greg Kroah-Hartman
EOL (maintained from February 2017 to May 2017)[316]

Old version, no longer supported: 4.11
000000002017-04-30-000030 April 2017[317]
4.11.12[318]
Greg Kroah-Hartman
EOL (maintained from April 2017 to July 2017)[318]

Older version, yet still supported: 4.12
000000002017-07-02-00002 July 2017[319]
4.12.13[320]
Greg Kroah-Hartman
Supported release

Current stable version: 4.13
000000002017-09-03-00003 September 2017[321]
4.13.2[3]
Greg Kroah-Hartman
Latest stable release

Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

text: Revision control[edit]

text: 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.

text: In 2002, Linux kernel development switched to BitKeeper, an SCM system which satisfied 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.

text: 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, 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.[322] Git soon developed into a separate project in its own right and gained widespread adoption.

text: Version numbering[edit]

text: The Linux kernel has had three different numbering schemes.

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

text: 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 even–odd version numbering scheme. The minor revision had been changed whenever security patches, bug fixes, new features or drivers were implemented in the kernel.

text: In 2004, after version 2.6.0 was released, the kernel developers held several discussions regarding the release and version scheme[324][325] 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.

text: 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.

text: On 29 May 2011, Linus Torvalds announced[326] 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; for example, 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; the Linux community refers to this as "x.y.z" versioning. The major version number was also later raised to 4, for the release following version 3.19.[327][b]

text: 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.

text: Timeline[edit]

text: Variants[edit]

text: There are certain variants of the Linux kernel that provide additional functionality, but do not belong to the Linux kernel mainline. Such variants of the Linux kernel include Linux-libre, Compute Node Linux, Cooperative Linux, Longene, grsecurity, INK, L4Linux, MkLinux, RTLinux, and User-mode Linux. Some of these variants have been partially merged into the mainline.[328]


document_title: Geography of Pakistan

question_text: what are the most fertile regions of pakistan

root

text: Geography of Pakistan

text: International boundaries[edit]

text: Pakistan shares its borders with four neighboring countries – Afghanistan, China, India, and Iran – adding up to about 6,975 km (4,334.1 mi) in length (excluding the coastal areas).

tag: p

text: Pakistan definitely borders Afghanistan at the Durand Line, 2,430 km (1,509.9 mi), which runs from the Hindu Kush and the Pamir Mountains. Its proposal was drafted by and named after the former secretary of British India Sir Henry Mortimer Durand. When Pakistan became independent in 1947 however, the legitimacy of the demarcation was questioned and disputed by Afghans and the Pakhtun or Pashtun tribes. Afghanistan claimed the border was imposed upon their weak nation by stronger influences and favoured the establishment of another separatist state to be called Pakhtunistan.[1] The Durand Line remained disputed until 1994 when it was finally accepted. A narrow strip of Afghan-occupied Gorno-Badakhshan territory called the Wakhan Corridor extends between Pakistan and Tajikistan.[2] From the eastern tip of the Wakhan Corridor starts the Sino-Pak border between the People's Republic of China and Pakistan spanning about 510 km (316.9 mi). It carries on south-eastward and ends near the Karakoram Pass. This line was determined from 1961 to 1965 in a series of agreements between China and Pakistan and finally on 03-03-1963 both the governments, of Islamabad and Beijing, formally agreed. It is understood that if the dispute over Kashmir is resolved, the border would need to be discussed again.[2]

text: The boundary with Iran, 909 km (564.8 mi), was first delimited by a British commission in the same year as the Durand Line was demarcated, separating Iran from what was then British India's Baluchistan province.[2] Modern Iran has a province named Sistan va Baluchistan that borders Pakistan and has Baluchis in an ethnic majority. In 1957 Pakistan signed a frontier agreement with Iran in Rawalpindi according to which the border was officially declared and the two countries haven't had this border as a subject of serious dispute at all. The Northern Areas has five of the world's seventeen highest peaks along with highest range of mountains the Karakoram and Himalayas. It also has such extensive glaciers that it has sometimes been called the "Third Pole". The international border-line has been a matter of pivotal dispute between Pakistan and India ever since 1947, and the Siachen Glacier in northern Kashmir has been an important arena for fighting between the two sides since 1984, although far more soldiers have died of exposure to the cold than from any skirmishes in the conflict between their National Armies facing each other.

text: The Pakistan-India ceasefire line runs from the Karakoram Pass west-southwest to a point about 130 kilometers northwest of Lahore. This line, about 770 kilometers long, was arranged with United Nations (UNO) assistance at the end of the Indo-Pakistani War of 1947–48. The ceasefire line came into effect on January 1, 1949, after eighteen months of fighting between Indian forces and Afridi tribals which Pakistan had sent to occupy Kashmir and was last adjusted and agreed upon by the two countries according to the Shimla Agreement of July 2, 1972 between Indira Gandhi and Zulfikar Ali Bhutto. Since then, it has been generally known as the Line of Control or the (LoC).

text: The India–Pakistan border continues irregularly southward for about 1,280 kilometers, following the Radcliffe line, named for Sir Cyril Radcliffe, the head of the British boundary commission on the division of the Punjab and Bengal provinces of British India on 13 August 1947.

text: The southern borders are far less contentious than those in northern Pakistan (Kashmir). The Thar Desert in the province of Sindh is separated in the south from the salt flats of the Rann of Kachchh (Kutch) by a boundary that was first delineated in 1923–24. After independence and dissolution of Empire, Independent and free Pakistan contested the southern boundary of Sindh, and a succession of border incidents resulted. They were less dangerous and less widespread, however, than the conflict that erupted in Kashmir in the Indo-Pakistani War of August 1965 started with this decisive core of issues. These southern hostilities were ended by British mediation during Harold Wilson's era, and both sides accepted the award of the Indo-Pakistan Western Boundary Case Tribunal designated by the UN secretary general himself. The tribunal made its award on February 19, 1968; delimiting a line of 403 kilometers that was later demarcated by joint survey teams, Of its original claim of some 9,100 square kilometers, Pakistan was awarded only about 780 square kilometers. Beyond the western terminus of the tribunal's award, the final stretch of Pakistan's border with India is about 80 kilometers long, running east and southeast of Sindh to an inlet of the Arabian Sea.

text: Maritime claims[edit]

text: Geographical regions[edit]

text: Pakistan is divided into three major geographic areas: the northern highlands; the Indus River plain, with two major subdivisions corresponding roughly to the provinces of Punjab and Sindh; and the Balochistan Plateau. Some geographers designate additional major regions. For example, the mountain ranges along the western border with Afghanistan are sometimes described separately from the Balochistan Plateau, and on the eastern border with India, south of the Sutlej River, the Thar Desert may be considered separately from the Indus Plain. Nevertheless, the country may conveniently be visualized in general terms as divided in three by an imaginary line drawn eastward from the Khyber Pass and another drawn southwest from Islamabad down the middle of the country. Roughly, then, the northern highlands are north of the imaginary east-west line; the Balochistan Plateau is to the west of the imaginary southwest line; and the Indus Plain lies to the east of that line.

text: The northern highlands[edit]

text: The northern highlands include parts of the Hindu Kush, the Karakoram Range, and the Himalayas. This area includes such famous peaks as K2[3] (Mount Godwin Austen, at 8,611 meters the second highest peak in the world). More than one-half of the summits are over 4,500 meters, and more than fifty peaks reach above 6,500 meters. Travel through the area is difficult and dangerous, although the government is attempting to develop certain areas into tourist and trekking sites. Because of their rugged topography and the rigours of the climate, the northern highlands and the Himalayas to the east have been formidable barriers to movement into Pakistan throughout history.

text: South of the northern highlands and west of the Indus River plain are the Safed Koh Range along the Afghanistan border and the Sulaiman Range and Kirthar Range, which define the western extent of the province of Sindh and reach almost to the southern coast. The lower reaches are far more arid than those in the north, and they branch into ranges that run generally to the southwest across the province Balochistan. North-south valleys in Balochistan and Sindh have restricted the migration of peoples along the Makran Coast on the Arabian Sea east toward the plains.

text: Several large passes cut the ranges along the border with Afghanistan. Among them are the Khojak Pass, about eighty kilometres northwest of Quetta in Balochistan; the Khyber Pass, forty kilometres west of Peshawar and leading to Kabul; and the Broghol Pass in the far north, providing access to the Wakhan Corridor.

text: Less than one-fifth of Pakistan's land area has the potential for intensive agricultural use. Nearly all of the arable land is actively cultivated, but outputs are low by world standards. Cultivation is sparse in the northern mountains, the southern deserts, and the western plateaus, but the Indus River basin in Punjab and northern Sindh has fertile soil that enables Pakistan to feed its population under usual climatic conditions.

text: The Indus plain[edit]

text: The name Indus comes from the Sanskrit word sindhu, meaning ocean, from which also come the words Sindh, Hindu, and India. The Indus, one of the great rivers of the world, rises in southwestern Tibet only about 160 kilometres west of the source of the Sutlej River, which first flows through Punjab, India and joins the Indus in Pakistani Punjab, and the Brahmaputra, which runs eastward before turning southwest and flowing through India and, Bangladesh. The catchment area of the Indus is estimated at almost 1 million square kilometres, and all of Pakistan's major rivers—the Kabul, Jhelum and, Chenab—flow into it. The Indus River basin is a large, fertile alluvial plain formed by silt from the Indus. This area has been inhabited by agricultural civilizations for at least 5,000 years.

text: Sistan Basin[edit]

text: Balochistan is located at the eastern edge of the Iranian plateau and in the border region between Southwest, Central, and South Asia. It is geographically the largest of the four provinces at 347,190 km² or (134,051 square miles) of Pakistani territory; and composes 48% of the total land area of Pakistan. The population density is very low due to the mountainous terrain and scarcity of water. The southern region is known as Makran. The central region is known as Kalat.

text: The Sulaiman Mountains dominate the northeast corner and the Bolan Pass is a natural route into Afghanistan towards Kandahar. Much of the province south of the Quetta region is sparse desert terrain with pockets of inhabitable towns mostly near rivers and streams. The largest desert is the Kharan Desert which occupies the most of Kharan District.

text: This area is subject to frequent seismic disturbances because the tectonic plate under the Indian plate hits the plate under Eurasia as it continues to move northward and to push the Himalayas ever higher. The region surrounding Quetta is highly prone to earthquakes. A severe quake in 1931 was followed by one of more destructive force in 1935. The small city of Quetta was almost completely destroyed, and the adjacent military cantonment was heavily damaged. At least 20,000 people were killed. Tremors continue in the vicinity of Quetta; the most recent major earthquake occurred in October 2008. In January 1991 a severe earthquake destroyed entire villages in the Khyber-Pakhtunkhwa, but far fewer people were killed in the quake than died in 1935. A major earthquake centred in the Khyber-Pakhtunkhwa's Kohistan District in 1965 also caused heavy damage.

text: Climate[edit]

text: Pakistan lies in the temperate zone, immediately above the tropic of cancer. The climate varies from tropical to temperate. Arid conditions exist in the coastal south, characterized by a monsoon season with adequate rainfall and a dry season with lesser rainfall, while abundant rainfall is experienced by the province of Punjab, and wide variations between extremes of temperature at given locations. Rainfall varies from as little as less than 10 inches a year to over 150 inches a year, in various parts of the nation. These generalizations should not, however, obscure the distinct differences existing among particular locations. For example, the coastal area along the Arabian Sea is usually warm, whereas the frozen snow-covered ridges of the Karakoram Range and of other mountains of the far north are so cold year round that they are only accessible by world-class climbers for a few weeks in May and June of each year.

text: Pakistan has four seasons: a cool, dry winter marked by mild temperatures from December through February; a hot, dry spring from March through May; the summer rainy season, or southwest monsoon period, from June through September; and the retreating monsoon period of October and November. The onset and duration of these seasons vary somewhat according to location.

text: The climate in the capital city of Islamabad varies from an average daily low of 5 °C (41.0 °F) in January to an average daily high of 40 °C (104 °F) in June. Half of the annual rainfall occurs in July and August, averaging about 300 millimetres (11.81 in) in each of those two months. The remainder of the year has significantly less rain, amounting to about 100 millimetres (3.94 in) per month. Hailstorms are common in early spring.

text: Pakistan's largest city, Karachi, which is also the country's industrial center, is more humid than Islamabad but gets significantly lesser rainfall. Only July and August average more than 50 millimetres (1.97 in) of rainfall in the Karachi area; the remaining months are exceedingly dry with little rainfall. The temperature is also more uniform in Karachi than in Islamabad, ranging from an average daily low of 13 °C (55.4 °F) during winter evenings to an average daily high of 34 °C (93.2 °F) on summer days. Although the summer temperatures do not get as high as those in Punjab, the high humidity causes the residents a great deal of discomfort.

text: Natural resources and primary industry[edit]

text: Water resources[edit]

text: Hydrological power is a renewable resource which benefits Pakistan a lot. After the Indus Water Treaty on 1960 World Bank decided that River Sutlej, Ravi and Beas water will be used by India and River Indus, Jhelum and Chenab water will be used by Pakistan. Pakistan was told to build 2 Dams one Tarbela And second Mangla, 5 Barrages, 8 Link Canals and one gated siphon. For this India was told to Participate 60% while Pakistan will participate 40%. Pakistan is considering to develop wind turbines to fulfill the demand for electricity.solar power is now slowly flourishing but it is still installed on a small scale.

text: Pakistan Largest River is known as River Indus which Flows from Tibet China and enters through Pakistan by Gilgit Baltistan. River Indus System is known as Indus System. It is divided into two plains. Upper Indus Plain starts from Northern Pakistan and ends up at Mithankot. River Indus has tributaries on both western and eastern side. River Indus eastern tributaries are River Jhelum, Chenab, Sutlej, Ravi and Beas. These four rivers flow in Punjab. These four rivers meet at Panjnad where they are known as River Panjnad. River Indus western tributaries are River Swat, Kabul, Kurrram, Tochi, Gomal, Zhob. These rivers join River Indus at KPK. At Mithankot these rivers finally meet with River Indus. After this River Indus flows alone through Lower Indus Plain. Lower Indus Plain Starts from Mithankot up to Thatta where River Indus meets with the Arabian Sea. This place is also known as Indus Delta.

text: Fuel resources[edit]

text: Pakistan has extensive energy resources, including fairly sizable natural gas reserves, petroleum oil reserves, coal fields and large hydropower potential.

text: Agriculture[edit]

text: About 26% of Pakistan's total land area is under cultivation and is watered by one of the largest irrigation systems in the world. The most important crops are tobacco, cotton, wheat, rice, sugarcane, maize, sorghum, millets, pulses, oil seeds, barley, fruits and vegetables, which together account for more than 75% of the value of total crop output.[4]

text: Fishery[edit]

text: Fishery and fishing industry plays an important role in the national economy of Pakistan. With a coastline of about 1046km, Pakistan has enough fishery resources that remain to be fully developed. It is also a major source of export earning.

text: Forestry[edit]

text: About only 4% of land in Pakistan is covered with forests. The forests of Pakistan are a main source of food, lumber, paper, fuel wood, latex, medicine as well as used for purposes of wildlife conservation and Eco tourism.

text: Mining[edit]

text: The Salt Range in the Potwar Plateau has large deposits of rock salt. Pakistan has extensive mineral resources, including fairly sizable reserves of gypsum, limestone, chromites, iron ore, rock salt, silver, gold, precious stones, gems, marbles, tiles, copper, sulfur, fire clay and silica sand.

text: Environment and conservation[edit]

text: The environmental issues is a great problem for the nature and nation of Pakistan and has been disturbing the balance between economic development and environmental protection. As Pakistan is a large importer of both exhaustible and renewable natural resources and a large consumer of fossil fuels, the Ministry of Environment of Government of Pakistan takes responsibility to conserve and protect the environment.

text: Current issues: water pollution from raw sewage, industrial wastes, and agricultural runoff; limited natural fresh water resources; a majority of the population does not have access to potable water; deforestation; soil erosion; desertification.

text: Natural disasters[edit]

text: Pakistan is subject to frequent earthquakes which are often severe (especially in north and west) and severe flooding along the Indus after heavy rains (July and August). Landslides are common in the northern mountains.

text: Protected areas[edit]

text: There are 15 national parks, 72 wildlife sanctuaries, 66 game reserves, 9 marine and littoral protected areas, 19 protected wetlands and a number of other protected grasslands, shrublands, woodlands and natural monuments.

text: International agreements[edit]

text: Pakistan is a party to several international agreements related to environment and climate, the most prominent among them are:

text:
Treaties and Agreements

Specific Regions and Seas
Law of the Sea, Ship Pollution (MARPOL 73/78)

Atmosphere and Climate
Climate Change, Ozone Layer Protection, Nuclear Test Ban

Biodiversity, Environment, and Forests
Desertification, Endangered Species, Environmental Modification, Wetlands, Marine Life Conservation

Wastes
Hazardous Wastes

Rivers
Indus Waters Treaty

tag: table

text: Suffix of regions and towns[edit]

text: Parts of region and settlement names:

text:
-abad (Urdu: ـ آباد ) means settlement or town. Example: Islamabad, Faisalabad.
-dera (Urdu: ڈیره ـ ) means settlement or town. Example: Dera Ismail Khan.
-garh (Urdu: ـ گڑھ ) means fort or settlement. Example: Islamgarh.
-goth (Urdu: ـ گوٹھ ) means settlement or town. Example: Yousuf Goth.
-istan (Urdu: ـستان ) means land. Example: Baltistan.
Khel or -khel (Urdu: خیل ) denotes a Pashtun sub-tribe. Example: Darra Adam Khel (Urdu: درہ آدم خیل).
-kot (Urdu: ـکوٹ ) means settlement or town. Example: Islamkot, Sialkot.
-nagar (Urdu: ـ نگر ) means settlement or town. Example: Islamnagar.
-pur (Urdu: ـ پُور ) means settlement or town. Example: Nasarpur.
-wal (Urdu: ـوال ) means settlement or town. Example: Khanewal.
-wala (Urdu: ـوالا ) means settlement or town. Example: Gujranwala.
-tando (Urdu: ٹنڈو ـ) means settlement or town. Example: Tando Allahyar.


document_title: Mail merge

question_text: what is the purpose of mail merge in ms word

text: Mail merge

text:
[hide]This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)

The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help to establish notability by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond its mere trivial mention. If notability cannot be established, the article is likely to be merged, redirected, or deleted.
Find sources: "Mail merge" – news · newspapers · books · scholar · JSTOR (January 2016) (Learn how and when to remove this template message)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (January 2017) (Learn how and when to remove this template message)

This article is written like a manual or guidebook. Please help rewrite this article from a descriptive, neutral point of view, and remove advice or instruction. (December 2017) (Learn how and when to remove this template message)

(Learn how and when to remove this template message)

text: Mail merge is a process to create personalized letters and pre-addressed envelopes or mailing labels for mass mailings from a form letter.[1] The feature is usually employed in a word processing document which contains fixed text (which is the same in each output document) and variables (which act as placeholders that are replaced by text from the data source). The feature dates back to early word processors on personal computers, circa 1980. WordStar was perhaps the earliest to provide this, originally via an ancillary program called Mail merge. WordPerfect also offered this capacity for CP/M and MS-DOS systems, and Microsoft Word added it later on.[2]

text: The data source is typically a spreadsheet or a database which has a field or column for each variable in the template. When the mail merge process is run, the word processing system creates an output document for each row in the database, using the fixed text exactly as it appears.

text: Overview[edit]

text: The mail merging process generally requires the following steps:

text:
Creating a Main Document or and the Template.
Creating a Data Source.
Defining the Merge Fields in the main document.
Merging the Data with the main document.
Saving/Exporting.

tag: ol

text: A common usage is for creating "personalized" letters, where a template is created, with a field for "Given Name", for example. The templated letter says "Dear <Given Name>", and when executed, the mail merge creates a letter for each record in the database, so it appears the letter is more personal. It is often used for variable data printing. It can also be used to create address labels from a customer relationship management database, or for mass emails with pertinent information in them, perhaps a username and password.