Linux Was Called 'Obsolete' in 1992; 25 Years Later Minix Runs in Your CPU
The 1992 Usenet debate where Andrew Tanenbaum called Linux's monolithic kernel obsolete is revisited, revealing how Linux came to dominate servers, phones, and supercomputers, while Minix quietly became the hidden OS inside Intel's Management Engine on hundreds of millions of x86 chips, making both architects unexpected winners.
The 1992 Usenet Debate: Tanenbaum vs. Torvalds
On January 29, 1992, in the comp.os.minix Usenet newsgroup, Professor Andrew Tanenbaum of Vrije Universiteit Amsterdam posted a critique titled "Linux is obsolete." Tanenbaum, author of the Minix teaching OS and a widely used OS textbook, argued that Linus Torvalds' monolithic kernel design was a step backward to the 1970s. He famously added: "You should be glad you're not my student; I wouldn't give a high grade for this design."
Torvalds, then a Finnish student, had released his kernel months earlier under the name "Freax" (later renamed "Linux" by FTP administrator Ari Lemmke). He responded the next day with a blunt rebuttal, citing Minix's practical limitations: poor multitasking performance, proprietary licensing (requiring purchase of Tanenbaum's book), and the fact that Linux already ran on real hardware while Minix did not. Torvalds declared: "Linux beats the pants off Minix in almost all respects."
Technical Core: Monolithic vs. Microkernel
The debate centered on kernel architecture. Tanenbaum advocated microkernels (like Minix), where only a tiny core runs in privileged mode and drivers, filesystems, etc., run as isolated user-space processes. Torvalds chose a monolithic kernel, where the entire OS runs in a single privileged address space.
The article illustrates the reliability difference with a concrete example: a buggy Wi‑Fi driver. In a monolithic kernel, a driver crash corrupts kernel memory and brings down the whole machine. In a microkernel, the driver runs as a separate process; its crash only restarts that driver, leaving the rest of the system unaffected.
Outcome After 25 Years: Visible World vs. Safety‑Critical World
Linux (monolithic) conquered the visible computing world: it powers the vast majority of servers, all Android phones (billions of devices), and all 500 of the world's fastest supercomputers. The x86 architecture Tanenbaum predicted would die became the industry standard for three decades.
Minix (microkernel) became the standard in safety‑critical domains where failure is unacceptable: automotive (QNX in millions of cars), aviation, medical devices, and defense. Formally verified microkernels like seL4 validate Tanenbaum's design philosophy.
The Hidden Twist: Minix Inside Intel's Management Engine
In late 2017, at the Embedded Linux Conference Europe, Google engineer Ronald Minnich revealed that since 2008 every Intel chipset includes a separate microprocessor called the Management Engine (ME). It runs at "Ring -3" — below the OS, hypervisor, and even System Management Mode — with full access to memory, network, and storage, even when the machine is powered off.
Since roughly 2015, the ME runs a customized, closed‑source version of Minix 3. Thus, on hundreds of millions of Intel‑based PCs and servers, beneath the user's chosen OS (Linux, Windows, macOS), sits Tanenbaum's teaching OS — deployed at a scale he never imagined.
Tanenbaum's Reaction
Tanenbaum learned of this from news reports, not from Intel. He wrote an open letter to Intel CEO Brian Krzanich, noting that Minix had been under a BSD license since 2000, so Intel needed no permission. He had even helped Intel engineers reduce Minix's memory footprint years earlier without knowing the purpose. His only regret: "Not a single person at Intel told me, not even out of courtesy."
Conclusion: Two Winners, One Machine
Linus won the argument he cared about: practical usability and ubiquity. Tanenbaum won the argument he cared about: elegant, fault‑isolated design for critical systems. History arranged a surreal convergence: the monolithic kernel runs in the light, the microkernel runs in the shadows — both inside the same x86 chips Tanenbaum once declared dead.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
dbaplus Community
Enterprise-level professional community for Database, BigData, and AIOps. Daily original articles, weekly online tech talks, monthly offline salons, and quarterly XCOPS&DAMS conferences—delivered by industry experts.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
