Linux Kernel History: Wetin Still Matter Today
Follow Linux kernel history from 0.01 to 7.x: GPL for 1992, the microkernel fight, Git, LTS releases, and how each choice still affect servers today.
The short version of Linux kernel history
Linux kernel history start from version 0.01 for September 1991 reach the 7.x series wey dey boot for servers today. The release list no be the interesting part. Na small number of decisions shape how e be, and each one still get effect for machine wey you rent this afternoon. Why new kernel dey needed at all for 1991 belong to the longer story of Unix, AT&T licensing and the lawsuit wey stall BSD.
Dates and version numbers for here come from kernel.org and the release history wey e publish. The current state, as of 13 November 2026: 7.0 arrive on 12 April 2026, 7.1 on 14 June 2026, 7.2 for middle of August 2026, and 7.3 on 18 October 2026. kernel.org list 7.4-rc2 as mainline and 7.3.4 as the current stable release. The 7.2 branch reach end of life with 7.2.15 on 1 November 2026.
Why di GPL choice for 1992 still matter
Version 0.01 publish for 17 September 1991 under licence wey Torvalds write by himself. E require make dem distribute the source, and e add one line wey matter pass: "You may not distribute this for a fee, not even 'handling' costs." For 1991, software dey ship for floppy disks, and copying and posting floppy disks dey cost money. That clause make commercial Linux distribution impossible.
E change am. Dem announce the move go GNU General Public License (GPL) for the 0.12 release notes for January 1992, and e take effect for 1 February 1992. Version 0.95, for March 1992, na the first release wey publish under am. Every business wey later build on Linux dey stand on top this change.
The kernel na GPL version 2 only, and e never move go version 3. Torvalds refuse am for 2007, mostly because of the anti-tivoisation rule for GPLv3. This rule require installation information for modified versions of covered code wey dem convey with consumer device, unless neither the supplier nor any third party fit install modified code, like code wey dem install for ROM. E see locked hardware as the manufacturer's own business. For 2017, kernel developers publish the Kernel Enforcement Statement. E borrow one part of GPLv3 anyway: person wey receive first notice of violation from copyright holder and fix am within 30 days go get their licence back permanently, instead of losing am immediately when the breach happen.
Two consequences follow for server. The kernel binary wey you boot carry right to the matching source, so nobody fit give you Linux kernel wey you no fit inspect or rebuild. And the copyright notice for the kernel talk say the licence no cover user programs wey use kernel services through normal system calls. Na why proprietary databases and monitoring agents fit ship for Linux without breaking anything. A permissive licence create the opposite pressure, and this difference good make you understand before you choose platform: see Linux and FreeBSD as server platforms.
Why monolithic kernel win for real
On 29 January 1992, Andrew Tanenbaum post one message wey get title "LINUX is obsolete" for comp.os.minix newsgroup. E make two claims. Monolithic kernels, wey drivers and filesystems dey run inside one privileged address space, na design from 1970s, while microkernels, wey dem parts dey run as ordinary processes, na the future. And Linux dey tightly tied to Intel 386, so e no go ever run for other platforms.
Portability claim get answer through porting. When version 1.2 release for March 1995, ports to DEC Alpha, MIPS, SPARC and Motorola 68000 family still dey under development. Version 2.0 for June 1996 na the first stable release wey support 64-bit Alpha together with 386, and by early 1997 SPARC don join dem as integrated port.
Design claim get answer through compromise. Linux never become microkernel. E get loadable kernel modules: object files wey you fit insert inside running kernel and remove again, so driver fit release separately from kernel binary.
lsmod | head
modinfo virtio_net | head -5lsmod dey list wetin load right now. modinfo dey print the file wey module come from and the parameters wey e accept. For virtual server, most of the disk and network path dey inside modules, na why one kernel image fit boot for hardware wey e never see before. Kernel only dey announce new hardware, while user space daemon dey decide which module to load and wetin to call the device. Na so device management come dey inside init system, and na part of why systemd come hard to avoid.
Modules give this flexibility without the cost wey microkernel design carry. If you isolate driver inside its own process, you must pay for context switch and message on every call, and for 1992 that cost big.
The cost wey Linux keep na the one wey you need plan for: module dey run with full kernel privileges, so bad module fit bring the whole machine down instead of only one process. Out-of-tree modules na where this problem dey show. Vendor driver wey no dey mainline must rebuild against every new kernel. Na this DKMS dey do during upgrade. If that build fail, the device simply no go dey available after reboot.
Why SMP take fifteen years to finish
Linux 2.0 for June 1996 na the first stable kernel wey support symmetric multiprocessing (SMP), meaning more than one CPU dey run one kernel. The first implementation use one lock, the big kernel lock (BKL), so only one processor fit dey inside kernel code at a time. So second CPU help workload wey dey calculate for user space, but e help workload of system calls very little, because those calls queue behind the same lock.
Removing that lock take fifteen years. Dem convert the remaining users to fine-grained locking, mostly through the work of Arnd Bergmann, and dem delete BKL for 2.6.39, wey release on 18 May 2011. Scheduler move for the same slow timeline: the O(1) scheduler for 2.6.0, the Completely Fair Scheduler (CFS) from 2.6.23 for 2007, and EEVDF, wey replace CFS for 6.6 in October 2023.
Na that work make 4 vCPU plan no strange today. E still show one limit wey you need know. For shared virtual server, your kernel schedule your threads, and hypervisor schedule your kernel. Run top and read the %st field. Steal time na CPU wey your kernel ready to use but the host give to another guest, so no tuning inside your kernel fit recover am.
Why 2.6 series change how dem dey build kernel
Before 2.6, version numbers dey come in pairs. Even second number mean stable series (2.4), while odd one mean development (2.5). Dem release 2.4 on 4 January 2001 and 2.6 on 17 December 2003, so users wait almost three years for the next stable series. Distributions no fit wait, so dem backport patches. Two vendors fit both ship "2.4", but the kernels fit differ by thousands of patches.
Dem drop this split after 2.6. Mainline now open merge window for about two weeks, accept new work, then run release candidates until things quiet down. After that, e release every 9 to 10 weeks, na the cadence wey kernel.org still document. The other part of the model start on 4 March 2005 with the first release of the stable tree. Na fix-only update for 2.6.11 be that, and Greg Kroah-Hartman and Chris Wright maintain am. Stable tree dey accept fixes and reject features.
One effect be say version number stop to be promise. 3.0, 4.0, 5.0 and 7.0 no be rewrites. Torvalds dey increase the first number when the second one grow reach level wey annoy am. Na why 7.0 follow 6.19 for April 2026. For server, wetin matter na which branch your distribution dey track, and whether that branch still dey receive fixes.
How the BitKeeper wahala produce git for April 2005
From February 2002, dem dey develop the kernel with BitKeeper, one proprietary distributed version control system from Larry McVoy company, BitMover, starting with the 2.5 series. BitMover give kernel developers free licence with conditions: you no fit work on competing version control tool, and you no fit reverse engineer BitKeeper. Plenty developers no like say dem dey build free kernel with tool wey dem no allowed to read.
E break for April 2005, after Andrew Tridgell demonstrate one program wey fit talk to BitKeeper repositories. BitMover call am reverse engineering and withdraw the free licence. The kernel lose its version control system for the middle of development cycle.
Work on git start for April 2005. Torvalds announce the break with BitKeeper on 6 April. On 7 April, git don dey self-hosting, meaning say git own history don already dey kept inside git. Torvalds announce the first successful git merge on 17 April. For June 2005, git manage release of 2.6.12. Torvalds hand maintenance over to Junio Hamano soon after, then go back to the kernel.
The design come directly from the problem: thousands of contributors, plus maintainers wey dey pull from each other across network wey nobody trust. Every object get name from hash of its content, so if you change one byte for old history, the name of every commit after am go change. Na why clone be evidence, no be claim. Every deploy pipeline, every configuration repository, the code host wey most teams dey push to and the git server wey you fit run by yourself grow from licensing argument about one kernel.
Wetín LTS model promise, and wetin e no promise
Mainline no be wetin you go run. Dem dey replace mainline release 9 to 10 weeks later. Stable tree dey carry fixes until the next mainline release, unless dem keep one branch as longterm. Longterm branches, wey dem usually write as LTS, dey carry fixes for years, and na those branches plenty distributions dey build on.
2.6.32, wey dem release for December 2009, na where this model prove say e work. RHEL 6, Debian 6, SUSE Linux Enterprise 11 SP1 and Ubuntu 10.04 LTS all ship am, and dem maintain the branch until March 2016, more than six years after e first appear. Red Hat go further and carry the 2.6.32-based kernel with its own backports until RHEL 6 leave maintenance phase for 2020. E still dey sell selected security and urgent bug fixes for RHEL 6 through paid Long-Life add-on, with yearly terms wey reach end of 2030. To reproduce that decade of support free na the main reason CentOS exist and Rocky Linux and AlmaLinux replace am.
The promise don change more than once. E first be two years, then six years for some branches. For 2023, stable maintainers reduce the default back to two years, because backporting into old trees dey cost maintainer time, and old branches no dey get enough real testing. On 25 February 2026, Greg Kroah-Hartman publish longer projections again, after discussion with the companies wey depend on those branches. But new longterm kernels still usually start with projected end of life of two years.
Di data wey dey behind dis chart
[
{
"kernel": "5.10",
"released": "2020-12-13",
"eol_projected": "Dec 2026",
"maintained_for": 6.0
},
{
"kernel": "5.15",
"released": "2021-10-31",
"eol_projected": "Dec 2026",
"maintained_for": 5.1
},
{
"kernel": "6.1",
"released": "2022-12-11",
"eol_projected": "Dec 2027",
"maintained_for": 5.0
},
{
"kernel": "6.6",
"released": "2023-10-29",
"eol_projected": "Dec 2027",
"maintained_for": 4.2
},
{
"kernel": "6.12",
"released": "2024-11-17",
"eol_projected": "Dec 2028",
"maintained_for": 4.1
},
{
"kernel": "6.18",
"released": "2025-11-30",
"eol_projected": "Dec 2028",
"maintained_for": 3.1
}
]kernel.org list 6 longterm branches as of October 2026. The oldest one, 5.10, go don carry fixes for 6.0 years when e end for Dec 2026. The newest one, 6.18, get projection to run until Dec 2028, wey be 3.1 years of fixes.
Read those dates as projections, no be contract. The 6.6 and 6.12 projections both move outward for February 2026, and dem fit drop a branch wey nobody dey use instead. Your distribution normally make the choice for you: Debian 13 ship 6.12, and Ubuntu 26.04 LTS ship 7.0. That gap na the practical meaning of the LTS against interim release question for server, and na wetin really change under you when you upgrade Ubuntu 24.04 to 26.04.
One trap come from this. uname -r for Ubuntu 24.04 dey print something like 6.8.0-51-generic. That one na upstream base plus the distribution own backports, so the number tell you where the branch start, no be which fixes dey inside am. Scanners wey judge kernel by version string dey raise false alarms against distribution kernels for exactly this reason.
Wetin kernel dey argue about right now
Two arguments dey active, and both na about who go do the work.
Rust enter as infrastructure for 6.1 for December 2022. For 7.0, dem remove the experimental label, so the kernel main languages na C, assembly and Rust. Building with stable Rust compiler dey already supported for 6.1: im Makefile set RUSTC_BOOTSTRAP=1 to enable unstable features for stable compilers. The disagreement na about maintenance. C maintainer wey change interface fit break Rust bindings wey dem no dey read, and the argument na about who suppose repair dem.
The second argument na AI contribution. Sasha Levin propose policy for July 2025, after machine-assisted patches start dey reach the lists in bigger numbers. Dem commit the document on 6 January 2026, and now e dey inside the kernel own process documentation for docs.kernel.org/process/coding-assistants.html. AI agent no suppose add Signed-off-by tag, because that line dey certify the Developer Certificate of Origin (DCO), and na only person fit certify am. Current kernel documentation no longer require Assisted-by tag; instead, e direct contributors to the tool-generated-content guidelines. Contributors still suppose explain how dem use tool for cover letters and changelogs. Generated code must dey compatible with GPL-2.0-only. The human wey send the patch go review am and carry responsibility for am.
The main pressure behind the policy na review time. Generating patch dey take seconds, but reviewing one fit take maintainer whole afternoon. Tag no fit solve that imbalance. Human sign-off dey preserve provenance: the history still dey record who sign for each change, and na this property DCO come protect for 2004.
Wetín this history mean for the server wey you rent
- Na the licence make you fit read and rebuild the kernel wey your provider boots, and na why proprietary software still dey run on top am.
- Na the monolithic design make one driver bug fit bring the whole machine down, and na why you must rebuild an out-of-tree module every time you upgrade the kernel.
- Na the release model make version number tell you small, while the branch and the end-of-life date tell you almost everything.
- The virtualisation type decide wetin you fit do at all: for KVM you boot your own kernel and load modules, but for container virtualisation wey dey share the host kernel,
uname -rdey show the host version, and permission to usemodprobeor change sysctls depend on the privileges and configuration wey the host give you.
FAQ
Why Linux kernel still dey GPLv2 and e no be GPLv3?
Torvalds reject GPLv3 for 2007, mainly because of the anti-tivoisation requirement. This requirement say supplier must provide installation information for modified versions of covered code wey consumer device carry, unless neither supplier nor any third party fit install modified code, like code wey dey installed for ROM. E see locked hardware as manufacturer business. Relicensing hard well-well for practice too, because thousands of contributors hold copyright for the kernel and no assignment agreement dey to fall back on. The kernel na GPL-2.0-only, so code wey GPLv3 alone cover no fit merge.
Linux kernel na monolithic kernel or microkernel?
Na monolithic kernel with loadable modules. Drivers and filesystems dey run inside kernel address space, and lsmod dey show the ones wey load now. The result na speed for one side and bigger blast radius for the other: faulty module fit panic the whole machine, while microkernel go lose only one process. This difference don reduce since 1992 through FUSE filesystems wey dey run for user space and eBPF programs wey kernel verify before e run dem.
Wetin be the difference between mainline, stable and longterm kernels?
Mainline na Torvalds tree. E dey release every 9 to 10 weeks, and new features first land there. Stable take one mainline release and receive bug fixes until the next mainline release, unless dem keep the branch as longterm. Longterm branches continue to receive fixes for years, and many distributions build their kernels on top of dem. kernel.org list the current longterm branches and the projected end-of-life date for each one.
Linux kernel dey accept code wey AI write?
Yes, under policy wey dem commit to for January 2026. Current kernel documentation no longer require Assisted-by tag. Contributors suppose explain where tool-generated content come from inside cover letters and changelogs. AI agent no suppose add Signed-off-by line, and generated code must work with GPL-2.0-only. Human submitter sign off, meaning say e review the patch and accept responsibility for am under Developer Certificate of Origin.
Which kernel version I suppose run for server?
For almost every case, na the one wey your distribution dey maintain. Distribution kernel na upstream branch plus backported fixes plus vendor testing. Na this one your provider images and support arrangements dey assume. Build newer mainline kernel when you need specific driver or feature. Before you commit to the new branch, check the end-of-life date.