From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] How Unix made it to the top
Date: Sat, 17 Dec 2016 21:48:55 -0800 [thread overview]
Message-ID: <6765d35491677b6b2ca2e5a49176ece794aaf07b@webmail.yaccman.com> (raw)
In-Reply-To: <201612170209.uBH29G4k022238@coolidge.cs.Dartmouth.EDU>
As a postscript, on at least one occasion, the speech was finished so
close to
the time of delivery that a helicopter was sent to land on the lawn at
Bell Labs
to pick up the large-print version so it would get to the CEO in
time...
Steve
----- Original Message -----
From: "Doug McIlroy" <doug@cs.dartmouth.edu>
To:<tuhs at minnie.tuhs.org>
Cc:
Sent:Fri, 16 Dec 2016 21:09:16 -0500
Subject:[TUHS] How Unix made it to the top
It has often been told how the Bell Labs law department became the
first non-research department to use Unix, displacing a newly
acquired
stand-alone word-processing system that fell short of the
department's
hopes because it couldn't number the lines on patent applications,
as USPTO required. When Joe Ossanna heard of this, he told them about
roff and promised to give it line-numbering capability the next day.
They tried it and were hooked. Patent secretaries became remote
members of the fellowship of the Unix lab. In due time the law
department got its own machine.
Less well known is how Unix made it into the head office of AT&T. It
seems that the CEO, Charlie Brown, did not like to be seen wearing
glasses when he read speeches. Somehow his PR assistant learned of
the CAT phototypesetter in the Unix lab and asked whether it might be
possible to use it to produce scripts in large type. Of course it
was.
As connections to the top never hurt, the CEO's office was welcomed
as another ouside user. The cost--occasionally having to develop film
for the final copy of a speech--was not onerous.
Having teethed on speeches, the head office realized that Unix could
also be useful for things that didn't need phototypesetting. Other
documents began to accumulate in their directory. By the time we
became
aware of it, the hoard came to include minutes of AT&T board
meetings.
It didn't seem like a very good idea for us to be keeping records
from
the inner sanctum of the corporation on a computer where most
everybody
had super-user privileges. A call to the PR guy convinced him of the
wisdom of keeping such things on their own premises. And so the CEO's
office bought a Unix system.
Just as one hears of cars chosen for their cupholders, so were these
users converted to Unix for trivial reasons: line numbers and vanity.
Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161217/17d89614/attachment.html>
next prev parent reply other threads:[~2016-12-18 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 2:09 Doug McIlroy
2016-12-18 5:48 ` Steve Johnson [this message]
2016-12-18 8:54 ` Kay Parker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6765d35491677b6b2ca2e5a49176ece794aaf07b@webmail.yaccman.com \
--to=scj@yaccman.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).