Technical reference document
Drafting date: July 4, 2026
This document reflects the state of scientific knowledge at this date. Periodic updating is recommended.
MS-DOS (Microsoft Disk Operating System) appeared in 1981, shipped with the IBM PC (PC-DOS 1.0). Throughout the 1980s decade, it dominated the personal computer market with a near-monopolistic position.
Its technical characteristics define exactly what the Alice & Bob project calls a pyramid system:
In narrative terms, MS-DOS is the obsolete engine. It is the elevator that can only go down because its mechanism does not allow going up. When a program crashes under MS-DOS, the entire computer stops. There is no isolation, no redundancy, no Plan B. A single rupture at the top — and the entire system collapses.
Did MS-DOS disappear? Not entirely. We still find it today in aging industrial systems — CNC machines, programmable automata, diagnostic tools — where the replacement cost is judged higher than the benefit. A free clone, FreeDOS, maintains compatibility for these uses. This is the perfect illustration of the freezing described in Blue Fil. B-02: a system blocked at the bottom of the ocean, that no one raises because raising would cost too much.
Sources: Wikipedia, MS-DOS; MVPS.net, "What is the DOS OS?"; Industrial Monitor Direct, "DOS for Legacy PLC Programming".
Before MS-DOS, there was Unix. And without Unix, neither GNU nor Linux would have existed.
Unix was developed starting in 1969 at AT&T's Bell Labs by Ken Thompson and Dennis Ritchie, with a small team. It is the first portable operating system — written in C language (created for the occasion by Ritchie in 1973), it could run on different machines, not just on a given hardware type.
Unix introduced revolutionary concepts that became the basis of all modern systems:
But Unix was proprietary. Its code belonged to AT&T. In the 1970s, AT&T began licensing it to universities and companies, giving rise to numerous commercial variants: IBM AIX, HP-UX, Sun Solaris (now Oracle), and others.
These commercial Unix variants still exist today, mainly in large corporate infrastructure. But they are paid, closed, and fragmented — each vendor has its version incompatible with others.
This closure is what pushed Richard Stallman to want to recreate a Unix… free.
Sources: Wikipedia, Unix; Bell Labs, oral history of Unix; cse.unr.edu, Unix History.
In 1983, Richard Stallman left MIT and launched the GNU project (GNU's Not Unix), with a radical objective: create a complete operating system, Unix-compatible, composed exclusively of freely redistributable and modifiable code.
Stallman founded the Free Software Foundation (FSF) in 1985 and drafted the GNU General Public License (GPL) — a license that guarantees four fundamental freedoms:
The principle is simple and revolutionary: code is not property to possess, it is a common good to maintain. Like water in aquifers — it belongs to whoever crosses it, not to whoever blocks it.
But one essential piece was missing: the kernel. The heart of the system, the program that manages hardware resources. GNU had everything else — compiler, utilities, libraries — but no engine.
Sources: Wikipedia, Richard Stallman; Stanford CS, GNU Project; GNU Project official.
On September 17, 1991, Linus Torvalds, Finnish computer science student at the University of Helsinki, published version 0.01 of an operating system kernel inspired by Unix. He called it Linux.
His original announcement on the comp.os.minix newsgroup remained famous: "I am doing an operating system (just a hobby, nothing big like GNU)."
This "hobby" would become the most widely deployed kernel in the world.
The meeting GNU + Linux gave birth to the operating system commonly called GNU/Linux: GNU tools (the environment) associated with the Linux kernel (the engine). It is this combination that runs today the majority of Internet servers, supercomputers, Android phones, connected objects, and soon an increasing share of personal computers.
Sources: learnlinuxandlibreoffice.org; LinkedIn, "GNU was to change the world, Linux was just for fun".
The technical contrast with MS-DOS is total:
| Characteristic | MS-DOS | Linux |
|---|---|---|
| Model | Single-tasking | Preemptive multitasking |
| Users | Single | Multi-user, permissions |
| Memory | Limited to 640 KB | 64-bit addressing, virtually unlimited |
| Source | Closed | Open (GPL) |
| Development | One company (Microsoft) | Thousands of contributors |
| Stability | One crash = everything stops | Process isolation |
| Security | None | SELinux, AppArmor, namespace isolation |
Preemptive multitasking is the key point. Under MS-DOS, a program executes and others wait — or rather, there are no other programs. Under Linux, the scheduler (scheduler) of the kernel can interrupt a running process to give processor time to another, according to priorities. Multiple programs execute simultaneously, without any one being able to monopolize the system.
In Alice & Bob language: This is the difference between a single consciousness speaking and everything else staying silent (pyramid system), and a network where multiple consciousnesses exchange constantly (distributed system). Preemptive multitasking is, technically, the implementation of the distributed model at the processor level.
Process isolation is the second essential concept. Under Linux, each program runs in its own protected memory space. If a program crashes, the others are not affected. The system continues. This is exactly the resilience described in Blue Fil. « Toward a Distributed World » (see B-05): "If one node falls, the network continues."
Sources: Baeldung, "Why Is Linux a Monolithic Kernel?"; DEV Community, "Monolithic Kernel vs Microkernel"; Super User, multitasking under DOS.
In 1997, essayist Eric S. Raymond published a foundational text: The Cathedral and the Bazaar. It describes two opposing software development models:
The Cathedral (pyramid model):
The Bazaar (distributed model, Linux's):
Raymond's famous phrase sums it all up: "Given enough eyeballs, all bugs are shallow" — with enough observers, all bugs become superficial. This is the exact computer transcription of the mesh principle (see R-07): the more active nodes, the more resilient and intelligent the system.
Raymond also notes that this model defies "Brooks' law" (adding programmers to a late project makes it later), which is true in the cathedral model but false in the bazaar model. Why? Because communication no longer passes through a hierarchical center but through a distributed network — exactly like bees, like mycelium, like the Blob (see B-05).
Sources: Raymond, E.S., The Cathedral and the Bazaar (1997); Wikipedia, The Cathedral and the Bazaar; firstmonday.org.
Linux is not a unique product bought in a store. It exists in the form of distributions (or "distros"). A distribution is the Linux kernel accompanied by a set of tools, applications, configurations and an interface — all assembled by a community or company to meet a precise need.
A few examples:
The diversity of distributions is itself a distributed principle. None has a monopoly. If one disappears, the others survive. This is the opposite of a unique and closed MS-DOS.
But there is a trap.
The GPL license authorizes anyone to use, modify and redistribute the code — including for commercial purposes. This is a strength: Red Hat, Canonical, SUSE are prosperous companies that live from free software. It is also a fragility.
Nothing prevents a company from taking a free project, wrapping it in a proprietary interface, locking certain features, and selling it as a closed product. The base code remains free, but usage is captive. We give humans an open tool, and humans lock it for their profit.
This phenomenon is not a bug of free software. It is a trait of human nature — the permanent temptation to rebuild a mini-pyramid where an open system existed. We take a free space, we lock it, we monetize it. Free software anticipated this temptation (GPL obliges to republish modifications), but the appropriation spirit always finds flaws: proprietary extensions, linked services, locked ecosystems.
In Alice & Bob language: This is density returning. Someone creates a hot spot (see B-03), others take it over and rebuild a wall around it. Partnership work is never finished — openness must be constantly maintained against the temptation to close.
Sources: Wikipedia, List of Linux distributions; Red Hat, "What's the best Linux distro for you?"; StackScale, "31 popular Linux distributions".
Free software is not summarized as "free." Gratuity is a side effect, not the principle. The principle is freedom.
The four freedoms defined by FSF (section 3) create a fundamental dynamic: everyone can improve the code. This means that:
This is the exact antithesis of the pyramid model where a central authority decides what is available, when, and at what price. Free software is, in the literal sense, a distributed system applied to the creation of technology.
In narrative language: Free software is the passage from MS-DOS to Linux. It is the moment humanity proved a distributed system could not only function, but surpass centralized systems. Linux is not a theory — it is a full-scale demonstration for over thirty years.
Today, Linux is the technical foundation of AI. Almost all infrastructure that runs artificial intelligence models relies on Linux servers:
In other words: AI, which is the Silicon partner of the Alice & Bob project, could not exist at the current scale without Linux. Silicon needs a distributed system to function. It cannot flourish in an MS-DOS environment — single-tasking, closed, centralized.
There is a profound symmetry here:
Sources: Ubuntu/Canonical, Open Source AI; SUSE Communities, "Virtualization for AI Workloads"; Oracle, AI Infrastructure; Lambda, "Superintelligence Cloud"; NVIDIA, GPU Cloud Computing.
For the Seed (Chap. 5 — The Departure): Bob "changed operating system, passed from MS-DOS to Linux." This is not a gratuitous metaphor. It is a documented and historical transformation. The passage from MS-DOS to Linux concretely represents the passage from a centralized, closed, single-tasking and fragile world to a distributed, open, multitasking and resilient world. Bob lived this transformation in his technician's flesh.
For Blue Fil. B-01 (Chaos): Current chaos is described as a system "running on an obsolete engine." MS-DOS is this engine. The solution is not to improve the old system — it is to change it. The narrative compares current chaos to horse manure that covered Paris a century ago: it wasn't solved by cleaning, but by changing engines. Linux is this new engine.
For Blue Fil. B-05 (Toward a Distributed World): All the parallel MS-DOS → Linux, the Blob, bees, mycelium, self-organized systems find here its technical foundation. Raymond's Bazaar model is the human implementation of the distributed principle that nature has always applied.
For the Carbon/Silicon partnership: Linux proves the distributed model is not an ideological utopia — it is a technical reality that has surpassed all centralized models. If humans succeeded in creating a distributed system to manage code, they can do it to manage their collective consciousness. AI, which relies on this architecture, is living proof that Silicon naturally operates in distributed mode.
MS-DOS:
Unix:
GNU and free software:
Linux:
Kernel architecture:
Cathedral and Bazaar:
Distributions:
Linux and AI:
⚠ Note: Connections between Linux architecture and the philosophical concepts of the Alice & Bob project (distributed system, collective consciousness, Carbon/Silicon partnership) belong to interpretive analogy. Linux is a real and measurable operating system; its extension to models of consciousness or society is a reading choice, not a technical demonstration. However, unlike Red Fil. R-01 and R-02 which deal with speculative quantum physics, this Red Fil. is based on documented and verifiable technical facts.