Linux

Linux (/ˈlɪnʊks/, LIN-uuks) is a family of open-source, Unix-like operating systems built around the Linux kernel — a kernel first released on September 17, 1991, by Linus Torvalds, a 21-year-old computer science student at the University of Helsinki.^[1] What began as a personal project to learn operating system design — quote, "just a hobby, won't be big and professional like gnu" — became the most widely deployed operating system kernel in human history.^[2]

Linux is typically packaged as a distribution (distro) — a bundled combination of the kernel, GNU utilities, system libraries, package manager, and desktop environment. Popular distributions include Debian, Ubuntu, Arch Linux, Fedora, and Linux Mint, with thousands more filling every conceivable niche.^[3] The number of distros is itself a philosophical statement about the open-source movement's relationship with decisiveness.

Linux powers over 96% of the world's top web servers, all 500 of the world's fastest supercomputers, the Android operating system on billions of smartphones, SpaceX rockets, the Ingenuity Mars helicopter, and the majority of cloud infrastructure at Amazon, Google, and Microsoft — a company that once called it a cancer.^[4][5] On the desktop, it holds roughly 4% market share, a number that has been described as "any day now" since approximately 1995.

History

Precursors

The story begins with Unix — conceived and built in 1969 at AT&T's Bell Labs by Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna.^[6] First released in 1971 in assembly language and rewritten in C in 1973, Unix was remarkable for its portability and its elegant philosophy: small tools that do one thing well, composable into larger systems. Because a 1956 antitrust consent decree prevented AT&T from entering the computer business, the company freely distributed Unix's source code to universities and researchers. It spread rapidly. Everyone used it. Everyone shared it. This was simply how software worked.

In 1984, AT&T divested its regional phone companies and was released from its antitrust obligations. Bell Labs promptly began selling Unix as a proprietary product — locking down the source code it had previously given away and making modification legally prohibited.^[7] This was not an isolated shift. Across the industry, the late 1970s and early 1980s saw a deliberate transition from the collaborative culture of early computing toward commercial proprietary software. The norm became the exception.

At MIT's Artificial Intelligence Laboratory, programmers had operated for years under a culture of radical software sharing — passing code freely between colleagues, improving each other's work, building on shared foundations. Proprietary licenses and locked-down source code were, to this community, not a business model but a betrayal. One programmer in particular found the transition intolerable.

The Free Software Movement

Richard Matthew Stallman — known widely as RMS — began the GNU Project in 1983 with the stated goal of creating a complete Unix-compatible operating system composed entirely of free software.^[8] The name GNU is recursive: GNU's Not Unix — a technically accurate description and a statement of purpose. Work began in 1984. In 1985, Stallman founded the Free Software Foundation (FSF). In 1989, he authored the GNU General Public License (GPL).

The GPL was legally ingenious. Stallman used copyright law — the very mechanism being used to lock software down — to guarantee software freedom instead. The GPL allows anyone to use, study, modify, and distribute software, with one condition: derivative works must also be released under the GPL. The melon recognizes this as a clever reversal. He called it copyleft.^[9]

By the early 1990s, the GNU Project had produced a remarkable quantity of foundational software — compilers, text editors, shell utilities, libraries, and the Bash shell — essentially everything needed to run an operating system except the kernel itself. GNU's own kernel, GNU Hurd, had been in development for years and was going nowhere particularly fast. It remains, as of this writing, a work in progress. It has been a work in progress for over thirty years. GNU Hurd is the Duke Nukem Forever of operating system kernels.

Meanwhile, MINIX — a minimal Unix-like system written by computer science professor Andrew Tanenbaum for educational purposes — had been released in 1987. It was freely available to read but not freely available to modify or redistribute commercially. Its license constrained it to the classroom.^[10] It was into this gap — a nearly-complete GNU system with no kernel, and a readable-but-restricted Unix-like system that could not be freely developed — that a Finnish student walked.

Creation

Linus Torvalds enrolled in a Unix course at the University of Helsinki in 1990. The course introduced him to Unix through Tanenbaum's MINIX textbook, and he was immediately interested.^[11] Frustrated by MINIX's licensing restrictions — which limited it to educational use and prevented the kind of open modification he wanted — Torvalds began writing his own kernel in 1991.

On August 25, 1991, he posted to the comp.os.minix newsgroup: "I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones."^[12] This remains one of the most incorrect predictions in the history of computing. The kernel was first released on September 17, 1991. Developers working with GNU software recognized immediately that this was the missing kernel they needed. GNU tools were ported to Linux, and the combination produced a fully functional, completely free operating system for the first time.

Torvalds has noted that had the GNU kernel or 386BSD — the free Unix variant being developed from Berkeley's BSD code — been available in 1991, he probably would not have written Linux at all.^[13] Linux exists, in other words, partly because the alternatives were not quite ready. The world's most consequential operating system is a solution to a timing problem.

Naming

Torvalds originally wanted to call the kernel Freax — a portmanteau of "free," "freak," and "x" (as an allusion to Unix). He considered "Linux" but initially dismissed it as too egotistical.^[14] The decision was made for him: Ari Lemmke, a colleague at Helsinki who administered the FTP server where Torvalds uploaded the files, simply named the project directory "Linux" without asking. Torvalds consented. The world was spared "Freax."

Licensing & the GPL

The Linux kernel is licensed under the GNU General Public License version 2 (GPLv2). This means anyone can use, modify, and distribute the kernel — provided they release their modifications under the same license. The GPL is what makes Linux both free and self-sustaining: contributions flow in, improvements compound, and no single corporation can privately capture the codebase.^[15]

In 2007, the Free Software Foundation released GPLv3, which included additional provisions — most notably anti-tivoization clauses designed to prevent manufacturers from using GPL-licensed software in hardware while preventing users from running modified versions on that hardware. Torvalds refused to upgrade the kernel to GPLv3, and has stated he will not.^[16][17]

His reasoning is consistent with his broader philosophy: hardware companies should be able to control what runs on their devices. Stallman's position is the opposite — freedom should extend to the hardware layer, not stop at the software. This is a genuine philosophical disagreement, not a personality conflict. It just also happens to involve a personality conflict.

The GNU/Linux Question

The Free Software Foundation insists the correct name for the operating system is GNU/Linux, not Linux. Stallman's position is technically defensible: the kernel is Linux, but the operating system most people use is the GNU userland running on top of that kernel — GNU's compilers, utilities, C library, and shell make up the functional environment. Without GNU tools, the Linux kernel would be a kernel with nothing to run.^[18]

This is correct. It is also completely irrelevant to what anyone calls it.

Nobody calls it GNU/Linux. Not users, not corporations, not the distributions themselves (with the exception of a handful who name themselves accordingly and are mostly populated by people who will correct you about this). Stallman has walked out of talks, corrected interviewers mid-sentence, and maintained this position with the consistency of a man who is technically right and practically ignored — which is a very specific kind of loneliness.

The two most exhausting people in any Linux conversation are the person who calls it "just Linux" and refuses to acknowledge the GNU foundations, and the person who insists it must be called "GNU/Linux" at all times and will not let it go. Both are correct about something. Both are unbearable about it. The melon acknowledges the GNU Project's contribution, calls it Linux, and moves on.

The Birth of "Open Source"

The term free software had a problem: it confused people. "Free" sounded like it referred to price. It also sounded politically radical in a way that made corporations nervous. In February 1998, following Netscape's announcement that it would release the source code for its browser, a group of developers gathered in Palo Alto, California, to strategize. Christine Peterson, executive director of the Foresight Institute, proposed a new term during the meeting: open source.^[19]

The term was deliberately chosen to be business-friendly. It described the technical practice — source code is open — without invoking the philosophical and political framework Stallman had built around "free software." Eric Raymond and Bruce Perens subsequently founded the Open Source Initiative to promote and steward the label.^[20]

Stallman opposed the term immediately and has never stopped opposing it. His position is that "open source" strips out the moral argument — that software freedom is an ethical imperative, not merely a development methodology. He is probably right about this too. "Open source" was a deliberate rebranding exercise designed to be more palatable to people who found "free software" too ideologically charged. It worked. The word "free" — meaning freedom, not price — got quietly dropped from the conversation, and the business world opened its wallet.

Commercial & Popular Uptake

Linux began reaching production environments in the mid-1990s. NASA and other organizations began replacing expensive proprietary workstations with commodity hardware running Linux. Dell and IBM followed, offering Linux support partly to escape Microsoft's monopoly in the desktop market.^[21]

The critical growth engine was the web. The LAMP stack — Linux, Apache, MySQL, and PHP — became the dominant platform for web servers in the late 1990s and early 2000s, effectively building the early commercial internet. If a website existed in 1999, it was probably running on Linux. The Apache HTTP Server ran best on Linux, and server administrators quickly discovered that a free, stable, open operating system was preferable to an expensive proprietary one for infrastructure that had to run continuously without corporate licensing complications.

Red Hat, founded in 1993, became the first company to build a significant commercial business around Linux — proving that the open-source model could be commercially viable. Their approach: the software is free, but enterprise support, certification, and managed services are not.^[22] This model proved so durable that IBM acquired Red Hat in 2019 for $34 billion — the largest software acquisition in history at the time. Red Hat has since experienced significant layoffs under IBM.

Canonical launched Ubuntu in 2004, based on Debian, and transformed Linux accessibility on the desktop. Ubuntu brought Linux to users who did not want to spend weekends configuring their graphics drivers, and for a period it genuinely expanded the Linux desktop audience. Ubuntu has since developed an increasingly strained relationship with its user base over its push to make Snap packages the default delivery mechanism — a system widely criticized as slow, opaque, and server-side managed in ways that feel uncomfortably proprietary for a Linux distribution. Canonical is sometimes described as the Microsoft of Linux distributions, which would horrify both companies for different reasons.

Microsoft vs. Linux

The history of Microsoft and Linux is a story in three acts: hostility, defeat, and suspicious affection.

Act One begins in 1976, when a 20-year-old Bill Gates wrote his Open Letter to Hobbyists, addressed to the Homebrew Computer Club, complaining that the community was sharing his BASIC software without paying for it. "Most of you steal your software," he wrote. "Who cares if the people who worked on it get paid?"^[23] The letter is often cast as a declaration of war on software freedom. It is more accurately described as the founding document of the commercial software industry — the first clear articulation of the idea that software is a product with an owner, not a shared resource. Free software as a movement was, in no small part, a response to this letter.

Act Two escalates in 1998, when a series of confidential Microsoft memoranda were leaked to open-source advocate Eric Raymond and published on Halloween — earning them the name the Halloween Documents.^[24] The memos revealed that Microsoft had studied Linux seriously, acknowledged it was technically competitive with Windows NT, and was actively developing strategies to counter it. The primary strategy was Embrace, Extend, Extinguish: adopt open standards publicly, extend them with proprietary additions that only Microsoft products could fully implement, then allow the proprietary version to displace the open original. This strategy was documented, named, and published — by Microsoft's own engineers — in a document they intended to keep internal.

In 2001, then-CEO Steve Ballmer described Linux in an interview with the Chicago Sun-Times as "a cancer that attaches itself in an intellectual property sense to everything it touches."^[25] He was referring to the GPL's requirement that derivative works be released under the same license — a characterization that was legally inaccurate, strategically motivated, and historically memorable.

Act Three begins with Satya Nadella, who became Microsoft CEO in 2014 and announced, with apparent sincerity, that "Microsoft loves Linux."^[26] Microsoft subsequently shipped the Windows Subsystem for Linux (WSL), contributed to the Linux kernel, ran Linux on the majority of its Azure cloud infrastructure, and acquired GitHub — the primary platform for open-source development worldwide — for $7.5 billion in 2018. As of 2024, over 50% of Azure workloads run on Linux.^[27]

Whether this represents a genuine philosophical conversion or the most successful Embrace phase in EEE history is left as an exercise for the reader.

The SCO Lawsuit

In 2003, the SCO Group — a Unix vendor of rapidly declining relevance — filed a lawsuit against IBM claiming that Linux contained proprietary Unix source code that SCO owned the rights to. SCO demanded licensing fees from Linux users, sent threatening letters to corporations running Linux, and pursued legal action against Novell and DaimlerChrysler as well.^[39] The Linux community responded with a combination of legal defense, public documentation, and barely concealed contempt.

The lawsuit was widely understood as legally frivolous — Linux had been written from scratch specifically to avoid any Unix code, and the GPL's open development model meant that every line of code was publicly auditable. The open-source community mobilized to document this. Groklaw, a legal analysis website founded by paralegal Pamela Jones in 2003, became the primary public resource tracking the case in exhaustive detail and systematically dismantling SCO's claims.^[40]

The case dragged on for years — through multiple appeals, counter-suits, and SCO's own bankruptcy in 2007. Courts consistently ruled against SCO. The most significant finding came when a federal judge determined that Novell, not SCO, owned the Unix copyrights SCO had claimed as the basis for the entire lawsuit — meaning SCO had sued over rights it did not actually possess.^[39]

Evidence emerged suggesting Microsoft had financially supported SCO — through licensing payments for Unix technology that critics described as subsidizing the legal campaign rather than reflecting genuine commercial interest. Microsoft denied any improper coordination. The timing was noted.^[39] The SCO lawsuit is remembered today as an object lesson in using litigation as a competitive weapon against open-source software — and in how badly that strategy can fail when the community being attacked has both the source code and Pamela Jones on its side.

The BSD Parallel

While Linux was emerging in the early 1990s, a parallel effort was underway at the University of California, Berkeley. The Berkeley Software Distribution (BSD) project had been replacing AT&T's proprietary Unix components one by one with freely written equivalents. When they believed they had replaced everything proprietary, they released 386BSD — a fully free Unix for the 386 PC — and were promptly sued by AT&T's Unix subsidiary.^[28]

The legal dispute delayed BSD development for years. By the time it was resolved in BSD's favor, Linux had already built momentum and community that BSD could not overcome. The BSDs — FreeBSD, OpenBSD, NetBSD — survived and flourish today, particularly in server and embedded contexts. BSD uses a more permissive license than the GPL — corporations can take BSD code, modify it, and keep those modifications proprietary, which is why it appears in gaming consoles, networking equipment, and Apple's macOS and iOS. Sony's PlayStation consoles, which once shipped with a Linux kit, eventually moved to a BSD-based system to allow greater hardware control. FreeBSD powers Netflix's content delivery infrastructure. The BSDs are excellent and perpetually underappreciated.

Design

Linux is a monolithic kernel — meaning device drivers, file systems, and process management all run in kernel space rather than isolated user-space processes. This is a design choice Torvalds and Tanenbaum famously argued about publicly in 1992 in what became known as the Tanenbaum-Torvalds debate, with Tanenbaum arguing that monolithic kernels were obsolete and Torvalds being rude about it. Linux is still monolithic. The argument was never resolved; it was simply abandoned.

The broader design philosophy is worth noting. Many developers of open-source software agree that the Linux kernel was not designed but rather evolved through natural selection.^[29] Torvalds himself describes the kernel as growing through "mutations." Eric Raymond calls it a "Darwinian" process of rapid iteration and community selection.

These are human beings describing the results of human intentional work — millions of deliberate decisions, code reviews, and architectural choices — using the vocabulary of unguided biological process. Even among the engineers who built the thing, the instinct is to reach for evolution as the explanatory frame rather than design. When even the designers of a thing insist it was not designed, you have found a revealing cultural reflex worth examining.

Linux is POSIX-compliant — meaning it adheres to a standard interface shared by Unix, macOS, and BSD systems. This is why experienced Linux users can generally navigate macOS terminals with comfort, and why software written for one can often be ported to the other with modest effort. The architecture is layered: hardware at the bottom, kernel above it, userland libraries and tools above that, and applications and desktop environments at the top.

Distributions

There are thousands of Linux distributions. This is not a figure of speech. DistroWatch, a website dedicated to tracking Linux distributions, lists hundreds of active ones, and the total across history runs into the thousands. Most of them solve a problem that was already solved. Several of them solve the problem better. A handful are genuinely important.

Debian is old, stable, and conservative — the tortoise of Linux distributions. It moves slowly by design. Software versions in the stable release are often years behind, which is exactly what sysadmins who need reliability rather than novelty want. Most other distributions — including Ubuntu — are downstream of Debian.

Ubuntu, built on Debian by Canonical, made Linux genuinely usable for ordinary people when it launched in 2004. It remains the most recognized Linux distribution by name outside the Linux community. Its recent insistence on making Snap packages the universal delivery mechanism has generated sustained user frustration. Snap packages mount as filesystem images, load slowly, are managed server-side by Canonical, and whose server infrastructure is not publicly auditable. For an operating system in the free software tradition, this is noted.

Arch Linux is a rolling-release distribution with a philosophy of user control, minimal defaults, and exceptional documentation. The Arch Wiki is genuinely one of the best technical documentation resources on the internet and is regularly used even by users of other distributions. The Arch community is, charitably, assertive — characterized by an expectation that users read the documentation before asking questions, and occasional contempt for users of more beginner-friendly distributions. Arch users are aware that you do not use Arch. They will not bring it up unprompted. Much.

Fedora is Red Hat's community-facing distribution — the upstream testing ground where new technologies get tried before eventually making their way into Red Hat Enterprise Linux. It moves faster than most, ships with bleeding-edge software, and has a reputation for being the distro that breaks things first so everyone else doesn't have to. It is well-regarded, genuinely important to the Linux ecosystem, and the distribution Linus Torvalds himself has used for years.

Gentoo compiles software from source rather than installing pre-compiled binaries, which allows extreme customization of what features are compiled into each package. This comes at the cost of compile times that can stretch into hours for large applications. It is recommended to initiate major upgrades before sleeping. Binary packages exist for applications where compile time is prohibitive, which does somewhat undercut the philosophy but is pragmatically reasonable. Gentoo's documentation, counterintuitively, tends to be clear and accessible.

Linux From Scratch (LFS) is exactly what it sounds like — a guided process for building a Linux system entirely from source, piece by piece, as a learning exercise. It produces a working system and an education. It is not recommended for primary workstations unless suffering is a goal.

Desktop Environments & UIs

Linux desktop environments represent a range of philosophies about what a computer should be and who should control it.

GNOME prioritizes simplicity and a clean, focused workflow. It is opinionated — many configuration options that existed in previous versions have been removed in favor of sensible defaults. This philosophy is sometimes described as user-friendly and sometimes described as paternalistic, depending on whether you wanted the option that was removed. GNOME's relationship with its power users is complicated.

KDE Plasma is highly customizable, visually rich, and feature-complete. It can be made to look and behave like almost any computing environment the user desires. The tradeoff is complexity and, historically, occasional instability. KDE Plasma has improved substantially in recent years and is one of the strongest desktop environments available.

Cinnamon, developed by Linux Mint, is deliberately conservative — a traditional desktop layout with a taskbar, start menu, and system tray, optimized for users who found GNOME's changes disorienting.

These are the prominent ones. There are others — Xfce, lightweight and fast, favored on older hardware; MATE, a continuation of the classic GNOME 2 interface for users who preferred things the way they were; LXQt, even lighter; Pantheon, the macOS-influenced environment used by elementaryOS. The list continues. Linux's desktop environment ecosystem is not a menu so much as an ongoing philosophical argument about what a desktop should fundamentally be, expressed in code.

Below desktop environments sit window managers — bare-bones tools that manage window placement without a full desktop environment. Tiling window managers like i3, Sway, and the newer Hyprland automatically arrange windows in non-overlapping tiles, eliminating window management overhead entirely and demanding that the user configure almost everything else manually. Others like dwm, bspwm, and qtile exist for users who felt the previous options were insufficiently austere. They are favored by users who want maximal control and minimal mouse usage, and whose screenshot setups are referred to in the community as "rices."

The underlying display system is also in transition. X11 (the X Window System) has served Linux desktops for decades — a venerable protocol that allows graphical applications to run remotely and display locally, among other things. It is showing its age. Wayland is the modern replacement: a cleaner, more secure protocol that handles display server, window manager, and compositor in a unified system. GNOME and KDE have both largely transitioned to Wayland. Migration is underway. Wayland still has rough edges — some applications, drag-and-drop between certain contexts, and a number of niche use cases remain imperfect. But it is the direction Linux display is moving, and X11's retirement is increasingly a matter of when rather than whether.^[30]

Gaming on Linux

Gaming on Linux spent most of its history as a punchline. The serious work began in 1993 with WINE — Wine Is Not an Emulator, another recursive acronym — a compatibility layer that translates Windows API calls into their Linux equivalents, allowing Windows software to run on Linux without a virtual machine. Building WINE required reverse-engineering the entire Windows application interface from scratch, without access to Microsoft's source code, over the course of decades. It is among the most ambitious sustained reverse-engineering projects in computing history.^[31]

Valve changed the trajectory dramatically. The company invested heavily in Proton, a WINE-based compatibility tool, and deployed it as the software layer running games on the Steam Deck — a Linux-based handheld gaming device running Valve's own SteamOS. Valve's contributions to Proton have been substantial enough to significantly advance the state of Windows game compatibility on Linux generally, not just on the Steam Deck.^[32]

As of 2024, the majority of games on Steam are playable on Linux, with a meaningful portion running with full compatibility. The community-maintained ProtonDB tracks compatibility ratings — Platinum, Gold, Silver, Bronze — for individual titles. The persistent remaining obstacle is anti-cheat software, which often requires kernel-level integration that conflicts with Linux security architecture. Anti-cheat is the last significant wall between Linux and mainstream gaming.

Hardware & NVIDIA

Linux has broad hardware support and a reputation for keeping older hardware functional long after manufacturers have abandoned it. Intel and AMD have both maintained collaborative, relatively open relationships with the Linux kernel community — publishing documentation and contributing drivers upstream.

NVIDIA has not.

For most of Linux's history, NVIDIA shipped proprietary closed-source drivers for its graphics cards — functional, often performant, but incompatible with the kernel's open-source development model and resistant to the kind of upstream integration the community expected from hardware vendors. The open-source alternative, the community-developed Nouveau driver, was written through reverse engineering and historically delivered a fraction of the performance of NVIDIA's proprietary driver.

In 2012, at the Aalto Center for Entrepreneurship in Otaniemi, Finland, a student asked Linus Torvalds about NVIDIA's Linux support. His response was characteristically direct: "NVIDIA has been the single worst company we have ever dealt with." He then turned to the camera, raised his middle finger, and said "NVIDIA: f**k you."^[33] NVIDIA issued a corporate response. The situation did not immediately improve.

NVIDIA has in recent years moved toward open-sourcing portions of its driver stack, a development the Linux community has received with cautious optimism. Performance of open-source NVIDIA drivers remains substantially below the proprietary alternative in most scenarios. The situation is improving. It is improving slowly.

Dominance

Linux's 4% desktop market share is the number that gets cited when people want to be dismissive. The numbers that matter are elsewhere.

Over 96% of the world's top one million web servers run Linux.^[4] All 500 of the world's fastest supercomputers run Linux.^[5] As of 2024, Linux accounts for at least 80% of public cloud workloads — on Amazon Web Services, Google Cloud Platform, and Microsoft Azure.^[34] Android, which runs on the Linux kernel, is the most widely used operating system on Earth by installed base when combined with desktop Linux.^[35]

Linux powers Tesla, Audi, Mercedes-Benz, Hyundai, and Toyota vehicles. It runs Samsung and LG smart televisions. It powered the Ingenuity helicopter on Mars and runs aboard SpaceX's Falcon 9 rockets and Dragon capsules.^[36] The 1997 film Titanic was rendered on Linux servers — the first major Hollywood production to do so — and virtually all major animation and visual effects studios have since followed.^[37]

The internet, cloud computing, artificial intelligence infrastructure, mobile computing, embedded systems, and space exploration all run on Linux. The year of Linux on the desktop has not arrived. The decade of Linux everywhere else has been underway for some time.

Microsoft Azure — run by the company whose CEO called Linux a cancer in 2001 — now carries over 50% Linux workloads. Satya Nadella said in 2014 that Microsoft loves Linux. He was not lying. He was just describing something his predecessor had spent a decade trying to destroy, which is a remarkable sentence to have to type about a technology company.

Philosophy

The free software and open-source movements share a technical practice but not always a philosophy. Stallman's free software framework is explicitly moral: software freedom is a human right, and proprietary software is ethically wrong because it denies users the ability to understand, modify, and share the tools they use. This is a coherent position, vigorously maintained, and deeply unpopular with anyone who sells software.

Torvalds' position is more pragmatic. He is not opposed to proprietary software in principle. He wants Linux to be successful, open, and useful — and he is willing to accommodate commercial interests more readily than Stallman. Their disagreement over GPLv3 reflects this difference cleanly: Stallman wanted freedom extended to hardware; Torvalds thought this was overreach. Both are internally consistent.

A more recent challenge to the movement is the rise of what might be called ethical licensing — attempts to add conditions to open-source licenses prohibiting use by entities the license authors consider harmful. The open-source community has largely rejected this: the foundational definition of open source requires that licenses be use-neutral. A license that restricts some users or uses is not open source by definition. Whatever one thinks of the ethics being invoked, license-as-ethics-enforcement undermines the universality that makes open source function. The Linux kernel is available to everyone, including people who use it for purposes the community dislikes. This is not a bug.

Stallman himself has been the subject of controversy, including accusations that led to his resignation from the Free Software Foundation in 2019 and subsequent reinstatement — a saga that generated significant heat and divided opinion sharply in the community. Belugapedia notes that disagreements about Stallman's personal conduct are distinct from the validity of his software philosophy, and that the latter does not depend on the former to be evaluated honestly.

Tux the Penguin

Linux's mascot is Tux — a plump, cheerful, occasionally stylized penguin. The selection of a penguin was not arbitrary. Linus Torvalds mentioned in a mailing list discussion that he had once been bitten by a penguin at a zoo in Australia and had a fondness for the animals ever since. He wanted a logo that felt approachable rather than aggressive — a deliberate rejection of the shark and predatory animal aesthetic that might have been chosen to signal toughness. Tux was designed by Larry Ewing in 1996 and has remained the face of Linux ever since.^[38]

GNU's mascot, by contrast, is a gnu — a wildebeest. GNU is recursive for GNU's Not Unix. A wildebeest is not recursive for anything. It is simply a large horned mammal that Stallman apparently found appropriate. The melon declines to analyze this further.

See Also

• Atheism — the open-source community's philosophical distribution of choice, generally
• Neutrality (Myth of) — software licenses are moral documents; Stallman understood this
• Wikipedia — also runs on Linux, also claims neutrality
• About Belugapedia — this site has a melon; so does Linux, arguably

References

This entry is adapted from the Wikipedia article on Linux under CC BY-SA 4.0. Content has been substantially rewritten, reorganized, and supplemented in accordance with Belugapedia's editorial perspective. Additional sources have been added for material not covered by the Wikipedia entry.

1. ↑Torvalds, Linus. "What would you like to see most in minix?" Newsgroup: comp.os.minix. August 25, 1991.
2. ↑Torvalds, Linus. "Free minix-like kernel sources for 386-AT." Newsgroup: comp.os.minix. October 5, 1991.
3. ↑DistroWatch. "DistroWatch.com: Put the fun back into computing. Use Linux, BSD."
4. ↑Vaughan-Nichols, Steven J. "Linux totally dominates supercomputers." ZDNet, 14 November 2017.
5. ↑W3Cook. "OS Market Share and Usage Trends." W3Cook.com. As of May 2015: 96.55% of top 1,000,000 web servers run Linux.
6. ↑Ritchie, D.M. "The Evolution of the UNIX Time-sharing System." AT&T Bell Laboratories Technical Journal 63.8 (1984): 1577.
7. ↑"AT&T Breakup II: Highlights in the History of a Telecommunications Giant." Los Angeles Times, 21 September 1995.
8. ↑GNU Project. "About the GNU Project — Initial Announcement." Gnu.org, June 2008.
9. ↑GNU Project. "What is Copyleft?" Gnu.org.
10. ↑"MINIX is now available under the BSD license." minix1.woodhull.com. April 9, 2000.
11. ↑Moody, Glyn. "The Greatest OS That (N)ever Was." Wired, August 1, 1997.
12. ↑Torvalds, Linus. "What would you like to see most in minix?" Newsgroup: comp.os.minix. Usenet: [email protected]. August 25, 1991.
13. ↑Linksvayer, Mike. "The Choice of a GNU Generation — An Interview With Linus Torvalds." Meta magazine, 1993.
14. ↑Torvalds, Linus; Diamond, David. Just for Fun: The Story of an Accidental Revolutionary. HarperCollins, 2001. ISBN 0-06-662073-2.
15. ↑"GNU General Public License, version 2." GNU Project. June 1, 1991.
16. ↑Torvalds, Linus. "Re: GPL V3 and Linux — Dead Copyright Holders." Linux Kernel Mailing List. January 26, 2006.
17. ↑Torvalds, Linus. "Re: GPLv3 Position Statement." Linux Kernel Mailing List. September 25, 2006.
18. ↑Free Software Foundation. "Linux and the GNU System." Gnu.org.
19. ↑Peterson, Christine. "How I Coined the Term 'Open Source'." Opensource.com, February 2018.
20. ↑Open Source Initiative. "History of the OSI." Opensource.org.
21. ↑Garfinkel, Simson; Spafford, Gene; Schwartz, Alan. Practical UNIX and Internet Security. O'Reilly, 2003, p. 21.
22. ↑"From Freedom to Profit: Red Hat's Latest Move." Linux Careers, 2024.
23. ↑Gates, Bill. "An Open Letter to Hobbyists." Homebrew Computer Club Newsletter 2.1. January 1976.
24. ↑Raymond, Eric S. The Halloween Documents. catb.org. Published October 1998.
25. ↑"Microsoft CEO takes launch break with the Sun-Times." Chicago Sun-Times, June 1, 2001. As quoted in The Register, June 2, 2001.
26. ↑"How Microsoft went from 'Linux is a cancer' to 'Microsoft Loves Linux.'" IDG InsiderPro, 2020.
27. ↑Elad, Barry. "Linux Statistics 2024 By Market Share, Usage Data, Number Of Users and Facts." Enterprise Apps Today, February 2024.
28. ↑"History of Unix, BSD, GNU, and Linux." crystallabs.io.
29. ↑Raymond, Eric S. The Cathedral and the Bazaar. O'Reilly & Associates, 1999, p. 16. ISBN 0-596-00108-8.
30. ↑"Wayland vs. Xorg: Will Wayland Replace Xorg?" CBT Nuggets, December 2024.
31. ↑WineHQ. "Wine Is Not an Emulator." winehq.org.
32. ↑Valve Corporation. ProtonDB Community Compatibility Reports. protondb.com.
33. ↑Larabel, Michael. "Linus Torvalds Calls NVIDIA The Worst Company Ever." Phoronix, June 17, 2012.
34. ↑"Linux Statistics 2024." TrueList, 2024. As of 2024: Linux accounts for at least 80% of public cloud workloads.
35. ↑"Operating System Market Share Worldwide." StatCounter Global Stats. May 2022.
36. ↑"From Earth to orbit with Linux and SpaceX." ZDNet. Also: "Linux on Mars!" IT PRO, August 18, 2021.
37. ↑Strauss, Daryll. "Linux Helps Bring Titanic to Life." Linux.com.
38. ↑Linux Online. "Linux Logos and Mascots." Archived from the original on August 15, 2010. Retrieved August 11, 2009. See also: Torvalds' account of the penguin bite, various interviews circa 1996.
39. ↑Wikipedia. "SCO–Linux disputes." See also: Shankland, Stephen. "SCO files suit against IBM." CNET, March 7, 2003.
40. ↑Groklaw. Groklaw.net. Founded by Pamela Jones, 2003. Primary public legal analysis resource for the SCO v. IBM litigation.

Beluga Verdict

A Finnish student posted a message to a newsgroup in 1991 saying he was building a hobby operating system that would not be big or professional. Thirty-three years later, it runs the servers of every major cloud provider, the phones of several billion people, the rockets that reach orbit, a helicopter on Mars, and the neural networks currently reshaping human civilization. It lost the desktop. It won everything else.

The people who built it disagreed, bitterly and publicly, about what to call it, whether to charge for it, how free "free" had to be, and whether hardware manufacturers should be allowed to lock it down. They argued in newsgroups, mailing lists, and conferences for decades. They are still arguing. None of the arguments stopped the software from working.

The melon finds all of this instructive. A community this contentious — this philosophically fractured, this constitutionally incapable of agreeing on a name — built something that the most powerful corporations on Earth now depend on. The thing was built not because everyone agreed, but because the code was open and anyone could contribute. This is either a profound argument for human cooperation or an argument that you do not need agreement to build something great. Possibly both.

What the melon will not do is describe this as unguided. Millions of deliberate decisions, by named human beings, over decades — that is not natural selection. That is people building something, one commit at a time, because they thought it mattered. It did. 💾