Bell Labs, UNIX, and the most productive group of nerds in history
Bell Labs, UNIX, and the most productive group of nerds in history
Field note. Every game server we run is, somewhere underneath, a Linux process. Linux exists because of UNIX. UNIX exists because of this lab. The lineage isn't trivia.
The story of modern computing has a center of gravity. It is a particular corporate research lab in New Jersey, in a particular era, with a particular small group of people. Bell Labs, late 1960s through the 1980s, where UNIX was created.
If you use Linux, macOS, Android, or any version of Unix-like systems (which is almost every server, almost every embedded system, and most mobile devices), you're using something that started in this lab. This article tells how.
Bell Labs, briefly
Bell Telephone Laboratories was the research arm of AT&T, the American telecommunications monopoly. Founded in 1925, it was for decades one of the world's most prolific research institutions. Bell Labs scientists invented or co-invented:
- The transistor (1947). Modern computing's foundational building block.
- Information theory (Shannon, 1948).
- The laser.
- The C and C++ programming languages.
- UNIX.
- Cell phone networks.
- Many fundamental contributions to digital signal processing, communications, semiconductor physics.
Nine Nobel Prizes in Physics, plus Turing Awards, Emmy awards (for picture compression), and many others.
The reason Bell Labs was so prolific: AT&T's monopoly status gave it stable revenue, and a settlement with the U.S. government (the Modified Final Judgment) restricted AT&T from many businesses but let Bell Labs operate as a long-term research institution. Scientists had decades of patient funding for "blue sky" research.
When AT&T was broken up in 1984 and Bell Labs' funding model changed, the era ended. Bell Labs continued (through various corporate transitions: Lucent, Alcatel-Lucent, Nokia) but lost its dominance. The 1970s remain its peak.
Multics and its failure
The story of UNIX starts with Multics, a project Bell Labs joined with MIT and GE in the mid-1960s.
Multics was an ambitious operating system. Time-sharing (multiple users on one machine), virtual memory, modular structure, hierarchical filesystem. Many ideas that are now standard were invented or popularized in Multics.
It was also slow, complex, and over-budget. Bell Labs pulled out in 1969.
A few researchers at Bell Labs (Ken Thompson, Dennis Ritchie, others) wanted to keep doing time-sharing OS work. Without Multics, they had to start over, with much less budget. They started building something simpler.
UNIX: the early years
Ken Thompson wrote the first version of UNIX in 1969 on a PDP-7 computer that was sitting unused at Bell Labs. The system was called UNIX (originally written as "Unics") in a sort of dig at Multics.
Initial UNIX was tiny:
- Hierarchical filesystem.
- Multiple processes.
- A simple command interpreter (the shell).
- A few dozen utility programs (
ls,cat,cp, etc.). - Written in assembly language.
Thompson's collaborator Dennis Ritchie added more. By 1971, UNIX ran on a PDP-11 and had been ported to the C language (which Ritchie developed in parallel; see the next article).
By 1973, UNIX was substantial enough to be useful. Bell Labs used it internally. The first version of UNIX outside Bell Labs went to the University of California, Berkeley in 1974.
The UNIX family tree
MULTICS (1965-69)
(Bell Labs withdraws)
│
▼
UNIX (1969, PDP-7)
│
1973 ── rewritten in C
│
┌───────┴───────┐
│ │
Research UNIX BSD UNIX (1977, Berkeley)
(Bell Labs) │
│ ┌────┼─────────┐
▼ ▼ ▼ ▼
System V FreeBSD NetBSD OpenBSD ── still maintained
(AT&T) │ MacOS Darwin (Apple)
│
▼
Commercial UNIXes
(SunOS, HP-UX, AIX, ...)
│
▼
Eclipsed by Linux ─────► Linux (1991)
+ Windows │
▼
Android, ChromeOS,
most servers, most
embedded systems
What UNIX did differently
UNIX wasn't the first time-sharing OS. It wasn't the most feature-rich. What set it apart was a set of design principles, captured later in "The UNIX Philosophy":
Small, focused tools. Each program does one thing well. ls lists files. grep searches. wc counts.
Composability via pipes. Programs can be connected so one's output is the next's input. ls | grep .txt | wc -l counts text files.
Everything is a file. Devices, sockets, even running processes appear as files in the filesystem.
Text streams as the universal interface. Programs read and write text, not binary blobs. Easy to combine.
Hierarchical filesystem. Everything organized in a tree.
These ideas seem obvious in 2026. In 1971, they were heretical. Many systems had monolithic applications doing everything. UNIX's tool-based philosophy was a different model.
The K&R book and C's universality
In 1978, Brian Kernighan and Dennis Ritchie published "The C Programming Language" (often called K&R). This 200-page book taught a generation of programmers C.
C had a few important properties:
Close to the hardware. Provided low-level operations (pointers, byte access) without forcing assembly.
Portable. Could be compiled for different architectures. UNIX was the first OS written largely in a portable language.
Simple. Small set of features, no built-in I/O (provided by library), no garbage collection.
Sufficient for systems programming. OS kernels, device drivers, language runtimes could all be written in C.
UNIX being written in C was decisive. To port UNIX to a new machine, you ported C, then recompiled UNIX. Other OSes of the era required massive assembly rewrites for each new architecture.
By the early 1980s, UNIX (in some variant) was running on dozens of different machine architectures.
Berkeley and BSD
Berkeley's graduate students extended UNIX significantly. Their work became BSD (Berkeley Software Distribution). Major BSD contributions:
- TCP/IP stack (1983, in BSD 4.2). The networking code that became the internet's foundation.
- vi text editor.
- csh and tcsh shells.
- NFS (Network File System).
- Sendmail.
BSD was free to anyone with a UNIX license from AT&T. By the mid-1980s, BSD UNIX was the dominant academic operating system in the U.S.
A legal dispute over BSD's freedom (USL v. BSDi, 1992-1994) eventually led to the FreeBSD, NetBSD, and OpenBSD projects, which are still maintained today. They're "Unix" in a strict legal sense.
AT&T's licensing
AT&T's antitrust settlement initially prevented it from being in the computer business commercially. So UNIX was licensed cheaply to universities. This is how UNIX spread through academia.
When AT&T was broken up in 1984, the company tried to commercialize UNIX. Prices for UNIX licenses rose sharply. Universities (including Berkeley) saw UNIX shift from "an academic curiosity" to "an expensive commercial product." The legal disputes around BSD followed.
This commercialization is partly what motivated the GNU project (1983) and later Linux (1991) to create freely-licensed UNIX-like systems. We'll get to GNU in the next articles.
The UNIX wars
By the mid-1980s, multiple companies were selling proprietary UNIX flavors:
- SunOS (Sun Microsystems).
- HP-UX (Hewlett-Packard).
- AIX (IBM).
- OSF/1 (Open Software Foundation).
- Ultrix (Digital).
- A/UX (Apple).
- SCO UNIX (Santa Cruz Operation).
- Xenix (Microsoft, sold to SCO).
Each variant was slightly incompatible with the others. The "UNIX wars" of the late 1980s and 1990s were vendor battles over which UNIX would win.
Effectively, none did. Linux (free) and Windows (proprietary) eclipsed them all by 2000. The remaining commercial UNIX vendors (Sun, IBM, HP) consolidated or moved to Linux.
What UNIX gave the world
Even beyond its specific code:
A culture. Small tools, plain text, command-line as primary interface, "this is fine, just script around it."
A skill set. Generations of engineers learned UNIX. Their habits and tools shaped subsequent systems.
A protocol model. Many later protocols (HTTP, SMTP, NNTP) inherited UNIX's text-based simplicity.
The pipes-and-filters architecture. Used in many systems beyond shells.
The "everything is a file" abstraction. Visible in many modern designs (Linux's /proc, /sys, etc.).
These ideas pervade modern computing. Most modern programmers absorb them without knowing the source.
The Bell Labs people
A few names worth knowing:
Ken Thompson. Wrote the original UNIX. Co-designed C (with Ritchie). Created Go (decades later, at Google). Built B (a predecessor to C). Turing Award 1983.
Dennis Ritchie. Co-designed UNIX. Designed C. Wrote the K&R book (with Kernighan). Turing Award 1983.
Brian Kernighan. Co-wrote K&R. Wrote AWK (with Aho and Weinberger). Designed Plan 9 (with Thompson, Pike, others). Many books.
Rob Pike. Worked on UNIX, Plan 9. Co-created Go (with Thompson and Robert Griesemer) at Google.
Bjarne Stroustrup. Created C++ (at Bell Labs, in the 1980s).
Doug McIlroy. Conceived UNIX pipes. Led the UNIX research group.
Joe Ossanna. Wrote troff and the early text-processing tools.
Many others. The Bell Labs Unix group at its peak was 10-20 people producing more important software than most companies of 1000.
Why this still matters
In 2026, the world runs on UNIX descendants:
- Linux (a UNIX clone) dominates servers, embedded systems, supercomputers.
- macOS (UNIX-certified, from a BSD/Mach base).
- Android (Linux-based).
- iOS (UNIX-based, related to macOS).
If you use a smartphone, you're using something whose ancestry traces to Bell Labs in 1969. If you use a server, almost certainly the same. The most common computing platform humans have ever invented is a recognizable descendant of what Thompson and Ritchie built.
Few research projects in history have had this kind of legacy.
The Bell Labs lesson
What enabled Bell Labs' productivity:
Patient funding. Long time horizons, not quarterly results.
Talent concentration. Smart, motivated people in one place.
Practical orientation. Build things that work, not just theory.
Freedom to fail. Multics failed; UNIX emerged.
Small teams. UNIX core was a few people. Many invention stories are similar.
These conditions are rare. Modern industrial research has mostly drifted toward shorter time horizons and more direct profit motivation. The patient long-term Bell Labs model has few imitators.
Whether such a model could be recreated today (in any industry) is a real question. The argument that it's worth trying is one of the lessons of UNIX's history.
Conclusion
UNIX is older than most of its users. It started small, at a research lab, with a few people who wanted to build a clean OS. It became, through decades of refinement and several major forks (BSD, Linux, GNU, the commercial UNIXes, Plan 9), the foundational software of modern computing.
The Bell Labs era is a model of what patient, well-supported research can produce. The modern world's most-used software is recognizably descended from a 1969 PDP-7 program written by Ken Thompson while his wife was on vacation.
Coming up
Next: the C language and why it's still everywhere. C is UNIX's sibling and almost as important. The story of how a small language built for a small OS became the lingua franca of systems programming.
Hosting your game server with AndroHost means we handle most of what's in this post for you automatically: tier sizing, SRV records, off-site backups, DDoS protection.
Keep reading
Today's centralization, when did the open internet become Cloudflare, AWS, and Google?
The early internet was a decentralized vision. Many small networks, many independent operators, no central authority. The end-to-end principle. Permissionless innovation.
IPv4 runs out, the 30-year scarcity timeline
The IPv4 address space has 4.3 billion addresses. By the 1990s, anyone paying attention could see they would run out. Anyone could predict roughly when. The transition to IPv6 was supposed to solve it. The transition started in 1996 and...
The cloud era, AWS, S3, and the death of the server room
In 2005, if you wanted to run a website at any scale, you needed servers. Physical machines, in a room you rented or owned, that you bought, configured, maintained, replaced. Setting up a startup's infrastructure took months and tens of...