The Linux creator
The Linux creator is Linus Benedict Torvalds, a Finnish software engineer who wrote the first commit of the Linux kernel on 25 August 1991 and has led its development, through 17 major releases and more than 4,000 active contributors, ever since.
He published the source code on a public Usenet newsgroup on 17 September 1991, an act that turned a personal hobby project into the operating system now running roughly 90 percent of the world's top servers. The story of how that kernel was built, and how the project has kept running without a single owner, is the story of the open source model put to its most demanding test.
Understanding the kernel's origin also means understanding the ecosystem it supports. Developers reach the same system through different Linux distros, from the lightweight Alpine used in containers to the long-support Ubuntu LTS that anchors most cloud deployments. Server-side web stacks and the Linux systems beneath them share the same syscalls and file system layout, which is why a PHP application behaves identically whether it runs on a 2 GB VPS or a 128 GB instance. The Linux Mint desktop distribution, a fork of Ubuntu that ships with a 24-month LTS cycle, is one of the most popular choices for people who want a familiar interface while running the same kernel that powers data centres. And for anyone working with the server-side stack, the practical path is to learn Linux for the LAMP stack, where the kernel, Apache, MySQL and PHP form a stack that still underwrites a large share of the commercial web.
Who created Linux and why
Linus Torvalds started the Linux kernel as a personal exercise in operating system internals, not as a commercial product. He was 21 years old, a student at the University of Helsinki, and working on a MINIX operating system assignment that he wanted to extend with a working terminal. In 1991 he wrote the first kernel code on a 386 DX/33 PC running a 100 MB hard drive and 4 MB of RAM, hardware that would have cost about 3,000 dollars at retail. The project had no budget, no roadmap and no second developer for the first several months. Torvalds chose to publish the code under what became the GNU General Public License version 2, a legal instrument that guaranteed every future user the right to read, modify and redistribute the source. That single licensing decision is the reason the project has outlived its creator's initial intentions by 3 decades.
The open source model that built the kernel
The open source model works through a central code repository, public mailing lists and a maintainership hierarchy that Torvalds has kept deliberately flat. The kernel development cycle runs on a 2 to 9 week merge window, after which a stable release is cut and bug fixes are backported for 2 to 3 years. The Git version control system, which Torvalds wrote in 2005 specifically to manage the kernel's merge traffic, now has more than 300 million repositories in use. Three governance layers keep the project coherent:
- The kernel maintainer, Torvalds, reviews and merges patches that touch core subsystems such as the scheduler, memory manager and virtual file system layer.
- Subsystem maintainers, of whom there are roughly 100, each own a tree such as networking, filesystems or hardware drivers and apply their own quality bar before code reaches the mainline.
- The Linux Foundation, incorporated in 2007, provides legal, trademark and event support without taking technical direction of the kernel.
Companies fund the model directly: Red Hat, Google, Amazon, Intel and Samsung all employ kernel engineers, and the Linux Foundation's annual survey of 10,000 developers in 2024 found that 96 percent of respondents used Linux in production.
From a 900-line hobby kernel to 30 million lines of production code
The growth of the code base follows the same open source pattern that created it. Linux 0.01, posted on 17 September 1991, was about 10,000 lines of C code and supported a single 386 machine. Linux 1.0, released on 14 March 1994, passed 170,000 lines and added a first set of device drivers and the ext2 file system. By Linux 2.6, released in 2003, the kernel had crossed 6 million lines and gained support for symmetric multiprocessing on up to 64 CPUs. The current mainline tree sits at roughly 30 million lines across 78,000 files, and the most recent stable release, Linux 6.1, shipped in 2024 with changes from contributors in 1,200 organisations. The 2.6 milestone in 2003 was the first release that most desktop users encountered, because it was the version that shipped inside Fedora Core 2 and Debian 3.1, the two distributions that defined the Linux desktop at the time.
Versioning and release cadence
The kernel follows a simple numeric scheme: major releases arrive roughly every 2 to 9 weeks, and the second digit in the version string marks the position in the cycle. A long-term support variant, designated by the kernel stable team, receives security and critical bug patches for a minimum of 2 years, extended to 3 years for the most recent LTS lines. Distribution vendors layer their own support on top: Ubuntu LTS releases, such as 22.04, carry 5 years of standard support and 10 years with the paid Extended Security Maintenance tier.
How the Linux kernel runs a modern server
The Linux kernel mediates every request between user space applications and the hardware, a job that becomes critical when a single server handles 50,000 concurrent connections. The process manager, the memory allocator, the network stack and the virtual file system are the 4 subsystems that a server-side workload touches on every request. Apache, Nginx, PHP-FPM and MySQL all call into the same set of roughly 350 POSIX syscalls, which means the configuration knobs that matter in production are kernel parameters, not application settings. The /proc and /sys virtual file systems expose 2,000 or more tunable values to administrators, from the TCP backlog queue depth to the page cache reclaim threshold. A sysadmin who understands those parameters can cut p99 latency by 15 to 30 percent on a busy LAMP node without touching a single line of PHP.
Why the project has outlasted its creator
Linux survives because no single person or company controls the code. Torvalds holds the final merge decision, but that authority is a technical role, not an ownership stake, and the kernel would continue if he stepped away tomorrow. The 4,000-plus active contributors span 1,200 organisations across 60 countries, and the patch queue averages 20,000 changes per merge window. The GNU GPL license, combined with the public development model, means that the 30 million lines of code are a shared commons that no vendor can fork and close. The same structure that made a 21-year-old's hobby kernel a global infrastructure project is the reason the Linux creator's original code base is now more resilient than most commercial software written with dedicated teams and multi-year contracts.