Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site masscomp.UUCP
From: trb@masscomp.UUCP (Andy Tannenbaum)
Subject: Political History of UNIX
Date: Sat, 25-Feb-84 18:45:05 EST
Posted: Sat Feb 25 18:45:05 1984
Date-Received: Sun, 26-Feb-84 04:55:17 EST
Organization: MASSCOMP, Littleton, MA
Below is a copy of the notes from my talk at this past USENIX in
Washington. It's in nroff -ms format, 304 lines.
Andy Tannenbaum Masscomp Inc Westford MA (617) 692-6200 x274
Political History of UNIX
Westford, MA 01886
This isn't a talk about how Ken Thompson and Dennis Ritchie hacked
their beloved and renowned PDP-7 to pieces in a tower on high.
I will not mention the extraordinary Bell Labs research environment -
crafty computer science gurus who took precious time off from
their highly important research efforts to help beat UNIX into shape.
I'm going to talk about some of the more earthly factors that
contributed to the UNIX that we know and love today. Perhaps after
hearing my story of how we got here, you'll be more able to follow in
their footsteps, bringing your own products similar fame and glory, or
at least you'll be better prepared to understand the results of UNIX's
There is an incredible number of people riding on the UNIX bandwagon,
the size of the UNIFORUM audiences is testament to that fact.
THE CABBAGE PATCH OPERATING SYSTEM
I sometimes think of UNIX as the Cabbage Patch Operating System.
UNIX wasn't a completely new idea, it was an amalgam of good ideas.
It's certainly the latest craze, with people foaming at the mouth
lining up in crazed hordes to get a peek, sometimes paying ridiculous
prices for an opportunity to use the product. Of course, they say,
it's worth it, there are lesser pleasures in life which are far more
Like the Cabbage Patch Kids, UNIX has existed for a while, lying
around in a relatively dormant state, waiting for the market to
Like Cabbage Patch Kids, every UNIX is slightly different (I'm sorry to
report) but they're all similar enough to be valuable as members of the
Cabbage Patch Kids are the product of a company
which doesn't specialize in dolls:
Lately Coleco (Connecticut Leather Company)
has been concentrating on the Adam computer and
Colecovision home video games.
Of course, UNIX is the product of another big toy company, AT&T.
WHAT TOOK SO LONG?
You might wonder what happened forces have tugged at UNIX during the
almost 15 years since UNIX was conceived.
Until recently, UNIX was never an AT&T OS product in the sense that VMS
was a DEC OS product. UNIX was always, AT&T would claim, a
telecommunications support tool, only because AT&T was a restricted
monopoly and it was forced by legal consent decree to stay out of the
This important idea here is that AT&T wasn't allowed to compete in the
computer marketplace, they weren't allowed to sell a product which
would compete with IBM or DEC or any of your companies. This caused
UNIX to grow up in unusual circumstances, with some benefits and some
In the case of most computer products, a computer company sees that the
marketplace yearns for a certain product or service, and then it
struggles to create that product or service before someone else does,
so that it might make a killing before the rest of the market produces
clones. This wasn't the case in the early days of UNIX, though it is
certainly the case today.
When UNIX left the caring hands of Thompson and Ritchie, it was soon
handed off to an entity called the UNIX Support Group (USG). The
people who controlled the progress of USG controlled the future
direction of UNIX through the 1970's.
HOW DID BELL USE UNIX?
Within AT&T, remember that UNIX was a tool, used by the Bell System
projects which dealt with research and development of different parts
of the telephone network - like switching, network planning, service
order processing, and directory production.
UNIX was the prize in a tug-o-war between these various projects,
UNIX was controlled by the telco projects with the most
bucks, projects like BANCS and 5ESS, and the BTL UNIX releases
sometimes had special purpose software in them with just these
projects in mind. These were not the needs of the programmer, or any
other common class of user, they were the specific needs of telco projects.
What was the Bell System going to do with UNIX?
Bell Laboratories had an enormous investment in expensive computer
equipment: IBMs, UNIVACs, Honeywells, and such. It was decided that
it would be efficient to have a coherent USER interface to all these
systems. What I'm trying to say here is that all the drones who
punched cards for the 360's got jealous of the UNIX users with their
timesharing terminals who didn't have to wait overnight for
job turnaround. Today it might strike you as strange that a Teletype
Model 33 user was a subject of envy: those days are gone indeed.
Anyway, one of the major UNIX forces at Bell Labs devoted itself to
producing PWB, the Programmer's workbench. Programmers would learn one
editor (ed) one command interpreter (sh) and be able to submit their
batch jobs over rje links from one UNIX terminal. UNIX was to have
COBOL syntax checkers and dump analyzers. The idea was to leave the
crunching to the big batch machines, and let UNIX front end handle the
Interestingly enough, I heard Bill Joy give a speech in Massachusetts where he
claimed that today's UNIX workstations should be used like yesterday's
terminals, and that our workstations should be networked to large
mainframe CPU's which can do the supercrunching. This philosophy is
not at all unlike that of PWB.
Within the Bell System, programmers used UNIX to talk to their IBM,
UNIVAC, and Honeywell mainframes.
The Bell System looked at UNIX as a small machine OS.
ARPA had different ideas, UNIX would be the successor to TENEX.
UNIX had no competition. Still doesn't. While this is nice, it does
tend to make people who protect and defend UNIX pretty soft.
UNIX SUPPORT GROUP
There was a UNIX SUPPORT GROUP, but you never heard about the
UNIX DEVELOPMENT GROUP. This is because no Bell System organization
had the charter to DEVELOP computer operating systems. There were
computer researchers, and there were people like USG who supported
telco projects. No one whose charter was development. People in
support positions are never given the respect that people in
development positions are given.
In the beginning of USG, the name UNIX had prestige, it was a clever
research toy. USG likewise had prestige, and there were clever
hackers working within USG. As UNIX within BTL became more of a
capitalist tool, the hackers likewise had to become capitalist tools,
there was less prestige in USG, less clever work to be done, the
hackers became disenchanted, and prestige and progressive development
within USG disappeared.
There was no screen oriented software or OS hacks because
no one had a charter to do it.
The political and philosophical powers didn't want it. Sort of like the
churches of the middle ages.
BELL AND BERKELEY
The UNIX development time line looked something like this:
research development maintenance panic-explosion
BTL didn't really have a distribution policy in the early days, you
got a disk with a note:
Here's your rk05, Love, Dennis.
If UNIX crapped on your rk05, you'd write to Dennis for another.
Sort of like human fsck.
There are USG UNIX User Meetings every six months, they used to always
be in a big auditorium at BTL Murray Hill. For a long time there was
always a carnival atmosphere at these meetings, there was always
plenty of room in the auditorium, most of the congregants had lots of
friends to yak with in the audience, similar to the early days of
One of the most amusing parts of the USG UUM's was the discussion of
the number of UNIX licenses that have been distributed outside the
Bell System. There was always a foil which described the Bell System
UNIX support policy:
no bug fixes,
payment in advance.
This slide was always greeted by wild applause and laughter, and, of
course, there were always twice as many licensees this year as the
year before. Not much to complain about.
The Bell System was fat and happy with its position in the UNIX
market. Send out some tapes, rake in some bucks, not a care in the
world. The USG were the Bell System's arrogant fat cats.
Then there was Berkeley. DARPA was UCB's Daddy Warbucks. UCB was a
scrappy little alley cat with some street smarts to get the job done
in the pinch. Where the Bell System sat on it's haunches, UCB used
some crazed grad student slave labor to whip up a product that the
Bell System would have taken forever to produce. The incentive just
wasn't there in the Bell System.
As long as UNIX ran on PDP/11's, UNIX was never taken seriously by
people with "real work" to do. No one really believed that you cold
actually PORT an operating system, it just wasn't done. The PDP/11
was nice and cheap, but you couldn't run big processes on it.
When the VAX came out, you could address memory out the wazoo. Not
only that, but a bunch of Bell Labbies actually PORTED UNIX to it, in
*NATIVE MODE* without a gargantuan effort. The VAX had virtual memory
and number crunching capability, and Berkeley had hackers interested
in exploiting it.
When the VAX 11/780 emerged as a UNIX workhorse, 4.1bsd emerged as the
UNIX system of choice for the VAX. Outside the Bell System,
practically no one ran Bell System UNIX on their VAXes. People would
buy a 32v UNIX system from WECo just for the license, they'd never even
read the tape, they'd then send their license to UCB and get a copy of
the latest BSD release.
Why? The UCB system was more programmer friendly. Eventually, it had
paging, job control, faster I/O and higher throughput, support for
many non-DEC I/O devices,
reasonable though not perfect support software like screen editors
and mailers, and compilers for languages like lisp and pascal.
UCB users were happy because they got the toys that they wanted to
Eventually, smart users throughout the Bell System were running
hacker-friendly 4bsd, and USG first responded with "it's not really
faster, it only SEEMS faster." Well, the hackers wanted a system that
Why couldn't the Bell System respond? In a nutshell,
BTL CS Research was too small and godly.
USG was too mundane.
There was nothing in between.
Yes, the Bell System does have an incredible record of innovation.
They have UNIX, as well as some lesser accomplishments like the
transistor and negative feedback, fundamental development of lasers
and Nobel prize-winning work in radio-astronomy. They even do some
Looking at it in another light, Bell Labs has more PhD's than any other
organization in the world. If I remember my propaganda correctly, they
have well over 7,000 PhD's, and another 20,000 engineers who can
actually get the work done. While the Bell System has been a leader in
innovation, they haven't done it by making efficient use of their
resources, and indeed they were never under any pressure to. For this
reason, a small and elite crew of hungry guerrillas like the UCB
students who worked on BSD were able to have a major impact on a small
piece of the Bell System's workspace.
What would have happened if there was a group of 20 hyperactive
hackers developing UNIX over the years?
The BTL environment consists of mostly telephony engineers, EE's with
communications backgrounds. They are ed users, 300 baud silent 700's,
tek graphics scopes. Well educated, but with poor understanding of
state of the art interfaces and very stubborn and arrogant. Ed and sh
are just fine, thank you.
Bell was not the SAIL/ALTO/MIT/ARPA LISP/EMACS DEC10 AI environment,
which is where much of the winning software from the 60's and 70's
came from. Maybe not AI, but at least some good software.
Dennis Ritchie says that BTLCS was waiting for a DEC10 that never got funded.
If they got it, UNIX would never have gotten off the ground.
What do we owe to the Bell System administrator who turned down the DEC10?
USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.
SCO Files Lawsuit Against IBM
March 7, 2003 - The SCO Group filed legal action against IBM in the State
Court of Utah for trade secrets misappropriation, tortious interference,
unfair competition and breach of contract. The complaint alleges that IBM
made concentrated efforts to improperly destroy the economic value of
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services
business. See SCO v IBM.
The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
Electronic mail: WorldWideWeb: