History · Information Technology · Software
The history of Unix: from a spare PDP-7 to everywhere
The most consequential operating system ever written started as a way to play a game cheaply. Out of an ambitious project called Multics, which Bell Labs left in 1969, two researchers at Bell Labs built something small, portable and generous - and it ate the world.
From the book The Operating System: Supervisor, Kernel, GhostChapters 7, 8, 9 and 10. Read the full book free as a PDF.
The cathedral Bell Labs walked away from
In the early 1960s, MIT's CTSS demonstrated that dozens of users could share one computer and each feel it was theirs. Multics - the joint project of MIT, Bell Labs and General Electric - set out to turn that trick into a computing utility for an entire community, as dependable as the telephone exchange. Multics overran its schedule and its budget. Bell Labs walked away in 1969; the project carried on elsewhere and Multics systems kept running commercially until 2000.
What survived was smaller and stranger. Ken Thompson found himself with ideas, time, and a problem: his game Space Travel, a simulation of the solar system, ran on a GE 635 where each run cost about seventy-five dollars of CPU time and the display was jerky. Scrounging, he found a little-used PDP-7, a small DEC machine with a decent display, and began moving the game to it.

Moving a program to a bare machine means writing everything underneath it. Thompson wrote, in assembly, a file system, an allocation scheme and a set of utilities - the scaffolding of an operating environment - to support one game on one orphan computer. Dennis Ritchie joined in. The little system got its name as a pun from Brian Kernighan: an emasculated, one-user echo of Multics - Unics, quickly respelled Unix. The first versions ran on the PDP-7 around 1969-70; the system then moved to the PDP-11 line and matured there.
A shed that outlasted the cathedrals
What Thompson and Ritchie carried out of the Multics project was a taste for small, sharp tools. Everything is a file: the disk, the terminal and later the network connection all answered to the same few operations - open, read, write, close. Programs were small tools chained by pipes, Doug McIlroy's 1972 suggestion, implemented overnight by Thompson, each program's output feeding the next one's input. Processes were cheap to create because on the PDP-7 they had to be. Where Multics had tried to design completeness in advance, Unix offered a few mechanisms that composed well and got out of the way.
The philosophy is usually quoted as "do one thing well", but its economic content is sharper: small, composable tools let users build what the designers did not foresee. That property - unanticipated composition - is the difference between a system and a platform, and it is why Unix-descended systems have hosted every computing fashion since, from workstations to the web to the cloud, without being redesigned for each.
The portability followed from the same discipline. Between 1969 and 1973 Ritchie developed the C language - low enough to touch the machine, high enough to ignore it - and in 1973 he and Thompson rewrote the Unix kernel in it. An operating system that could be recompiled for a different computer was a near-scandalous idea at the time. It meant the software no longer died with the hardware.
The great escape
Unix's second birthplace was an accident of law. AT&T, Bell Labs' parent, was a regulated telephone monopoly bound by a 1956 consent decree that kept it out of the computer business. It could not sell Unix, so it licensed the system to universities for a nominal fee, source code included. A generation of students grew up reading a real operating system's innards - John Lions's line-by-line commentary on Unix Version 6 became probably the most photocopied operating system text ever. At Berkeley, students led by Bill Joy turned their tape into the Berkeley Software Distribution, adding virtual-memory paging and, fatefully, the TCP/IP networking code that made Unix the native language of the growing internet.
When AT&T's empire was broken up in 1984 and the company could finally sell Unix, the lawyers followed: Unix System Laboratories sued Berkeley Software Design and the University of California in 1992, claiming the freely redistributable BSD code was tainted. The suit settled in 1994 and BSD lived on - its modern descendants run Netflix's content servers (FreeBSD) and supply the world's most-used remote-login software (OpenBSD's OpenSSH), and through NeXTSTEP the BSD line runs inside every Mac, iPhone and iPad. But the legal shadow had already made room for something with no AT&T code at all: a Finnish student's hobby kernel, told in how GNU and Linux became the world's default.
What survived
Ritchie and Thompson's account, in its 1978 revised form, counts more than 600 Unix installations, most of them in universities. Fifty years on, the count is in the billions. The design decisions that look technical were temperament made into software: two programmers who had watched a cathedral project end at Bell Labs built a shed, and the shed's descendants and imitators now run - as macOS, iOS, the BSD family, and the Unix-like Linux under Android - almost everything except the desktop. The slogan later attached to the philosophy, "worse is better", is usually misread as an excuse for shoddiness. Its actual claim is sharper: a system simple enough to be ported, taught and repaired by ordinary programmers will outrun a perfect system that only its authors understand. The fifty years since are the demonstration.
Quick answers
Who created Unix?
Ken Thompson and Dennis Ritchie at Bell Labs, beginning in 1969 on a cast-off PDP-7, after Bell Labs withdrew from the Multics project. Brian Kernighan coined the name.
Why was Unix rewritten in C?
An operating system written in assembly is welded to one machine. The 1973 rewrite in Dennis Ritchie's C language made Unix portable - the software could outlive and outmove its hardware, which had rarely been asked of an operating system.
Is Unix still used today?
Unix descendants and Unix-like systems run most of computing: the BSD family runs inside macOS, iOS, Netflix's servers and much network equipment, while Linux, written independently as a Unix-like system, powers servers, supercomputers and Android. The original AT&T code is gone, but the design won.
