Richard Stallman and GNU

Zusammenfassung

Richard Stallman built the tools that run the world’s software infrastructure — GCC, bash, GNU Emacs, GNU Make, glibc — and then watched Linux, not GNU, receive the credit. He invented copyleft, a legal mechanism that turned copyright law against itself to enforce software freedom. He articulated a philosophical position — that software freedom was a moral imperative, not a pragmatic preference — that split the open-source community between his “free software” framing and Eric Raymond’s “open source” framing. He was the most influential programmer of his generation who also polarized everyone who knew him, admired and alienated simultaneously. His tools are on every Linux system. His movement is contested. His legacy is unambiguous.

The MIT AI Lab and the Xerox Printer

Richard Matthew Stallman was born in Manhattan, New York on March 16, 1953. He was a mathematics prodigy who entered Harvard in 1971 and began working as a programmer at MIT’s AI Lab in 1971, near the end of his first year, while continuing his studies. He graduated magna cum laude with a Bachelor of Science in physics from Harvard in 1974, then enrolled as a graduate student in physics at MIT — but dropped out of the doctoral program after a year to work full-time at the AI Lab.

The MIT AI Lab of the early 1970s was one of the centers of hacker culture — a community of programmers who freely shared code, modified each other’s work, and regarded proprietary software as an antisocial hoarding of resources. Code in this environment was communal property. This was not a legal position — copyright applied to software — but a cultural norm so strong that it was taken for granted.

The norm collapsed around Stallman gradually through the late 1970s and early 1980s as the software industry commercialized. The incident he repeatedly described as the catalyst:

In 1980, Xerox donated a new laser printer to the AI Lab. The printer was faster than its predecessor but had a frustrating tendency to jam and provide no notification. Stallman wanted to modify the printer’s software to display jam alerts on users’ terminals — a modification he had made to the AI Lab’s previous printer. Xerox had not provided source code.

Stallman tracked down a researcher at Carnegie Mellon who he believed had access to the Xerox printer source code. The man refused to share it: he had signed a non-disclosure agreement.

Stallman described this as a moral injury. The man had placed his contractual obligation to a corporation above his obligation to a fellow programmer and the broader community. He had made a promise that caused harm to others.

GNU and the GPL

In September 1983, Stallman announced the GNU Project (“GNU’s Not Unix”) — a project to build a complete free operating system compatible with Unix. “Free” meant free as in freedom: users would have the right to run, study, modify, and redistribute the software. Stallman published the GNU Manifesto in 1985.

To enforce software freedom legally, he invented copyleft — a mechanism that used copyright law against itself. The GPL (GNU General Public License) was copyleft’s implementation: anyone who distributed GPL-licensed software had to make the source code available to recipients, and any modified version they distributed had to carry the same license. Freedom was self-replicating. You could not take GPL software, improve it, and sell the improvements without sharing them.

The GPL came in three major versions:

GPL v1 (1989): established the copyleft mechanism
GPL v2 (1991): added the “liberty or death” clause — if patent constraints prevented GPL compliance, distribution was prohibited entirely
GPL v3 (2007): addressed software patents, digital restrictions management, and the “Tivoization” problem (hardware that ran GPL software but prevented user modifications)

Linus Torvalds chose GPL v2 for Linux and has consistently refused to upgrade to GPL v3, partly over the anti-tivoization provisions. The resulting tension between Stallman’s more absolutist position and Torvalds’ more pragmatic one has been a persistent feature of open-source politics.

GNU Emacs and GCC

The GNU Project’s practical output was substantial:

GNU Emacs (1984) — the second version of the Emacs editor Stallman had written at MIT. Emacs was not just a text editor; it was a complete Lisp computing environment in which the editor itself was programmed. Every behavior was customizable. Users wrote substantial applications — mail clients, news readers, calendar systems — inside Emacs. It remained the preferred editor of many Unix programmers decades after its release.

GCC (GNU C Compiler) (1987) — a free, high-quality C compiler that was the technical foundation of the GNU ecosystem. Writing GCC was the hardest part of the GNU Project: a compiler required enormous engineering effort and had to produce code competitive with the proprietary Unix compilers it was replacing. GCC eventually supported C++, Fortran, Ada, and dozens of other languages, and became the compiler used by Linux and most of the open-source world.

glibc, bash, GNU Make, GNU Binutils — the complete toolchain without which a Unix-like system could not function. When Torvalds wrote the Linux kernel in 1991, he built it with GCC, linked it against GNU libraries, and ran GNU bash. The “Linux operating system” was substantially GNU tools running on a Linux kernel.

This is why Stallman insists on calling it GNU/Linux — and why most users call it simply Linux, to his perennial frustration.

The Free Software / Open Source Split

In 1998, Netscape released the source code to its Navigator browser under an open-source license. Eric Raymond and Bruce Perens saw an opportunity: if they could present the practical benefits of open-source development to corporations without the ideological baggage of Stallman’s free software framing, they could accelerate adoption.

They coined “open source” as an alternative term that emphasized development methodology and practical benefits — better code through more reviewers, no vendor lock-in — rather than Stallman’s moral argument about software freedom.

Stallman rejected the reframing then and has never accepted it since. His argument: the practical benefits are real but secondary. The fundamental issue is whether users control their computing or are controlled by their software. “Open source” obscures this by treating software freedom as a development methodology rather than a user right.

Free Software vs. Open Source in Practice

The practical overlap is large: the Free Software Foundation’s “four freedoms” (run, study, modify, distribute) are compatible with the Open Source Initiative’s definition. Most software that qualifies as “open source” also qualifies as “free software.” The difference is philosophical framing and licensing edge cases. Stallman considers licenses that restrict some commercial uses (Creative Commons NC, Business Source License) acceptable to open source advocates but violations of software freedom. The distinction matters most in political and legal advocacy contexts.

Resignation and Reinstatement

In September 2019, an email from Stallman became public in which he defended aspects of the behavior of Jeffrey Epstein associate Marvin Minsky. The characterization was widely condemned. Stallman resigned from the MIT Computer Science and Artificial Intelligence Laboratory and from the Free Software Foundation.

In March 2021, the FSF board reinstated Stallman as a board member. A public letter signed by thousands of developers and organizations — including major Linux distributors and open-source foundations — called for his permanent removal. The board retained him. The controversy remains unresolved.

Dead End: GNU HURD

The GNU Project’s intended kernel — GNU HURD — was designed to be a microkernel-based system more architecturally sophisticated than Linux. It has been in development since 1990 and remains in alpha. Linux, which was not the kernel Stallman intended, is what runs the world.

The Kernel That Wasn’t

HURD’s design (based on the GNU Mach microkernel) was technically ambitious and practically intractable. Microkernel performance challenges, debugging complexity, and the difficulty of coordinating volunteer contributors on an unglamorous kernel project left it perpetually incomplete. When Linux arrived in 1991, it provided a working kernel for the GNU userspace tools immediately. The pragmatic combination of Linux kernel and GNU tools succeeded; the philosophically pure GNU system was never finished.

The open-source movement’s development and commercial success is covered in The Open Source Revolution and The Open Source Business Model.