The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: aek@bitsavers.org (Al Kossow)
Subject: [TUHS] Ideas for a Unix paper I'm writing
Date: Tue, 28 Jun 2011 08:22:24 -0700	[thread overview]
Message-ID: <4E09F1B0.90805@bitsavers.org> (raw)
In-Reply-To: <20110628001140.GA23711@minnie.tuhs.org>

On 6/27/11 5:11 PM, Warren Toomey wrote:
> All, IEEE Spectrum have asked me to write a paper on Unix to celebrate the
> 40th anniversary of the release of 1st Edition in November 1971. I'm after
> ideas&  suggestions!
>

The notion that Unix provided a good enough set of system services that people
got on with building systems with a common set of tools. This included things
like the RATFOR-based portable operating systems that came out of Georgia Tech
and Laurence Livermore Labs. It took most of the 70's to get going, but by the
80's microprocessors were powerful enough that Unix would run well on them, and
that dovetailed with Stallman's efforts to get a freely available tool chain.

Contrast this with VMS/WinNT and the dozens of proprietary systems which survived
by vendor lock in.

Having lived through the OS wars inside Apple, it became clear that there weren't
enough developer resources available to build a new system from scratch, and the
value added wasn't in the core OS and tools, but the user environment. This appears
to have occurred to almost everyone else now as well. Go for product differentiators
and leverage as much freely available system infrastructure as you can.

I was just digging through some CDC documents we just received concerning the joint
CDC/NCR developments that happened in the early 70's, and was thinking how fast the
pace of system change is now. The system they started on in 1973 was ultimately
released almost 10 years later as the CYBER 180. By the end of the 80's they were
thinking of porting Unix to it. I can't imagine anyone taking 10 years today to
develop a new computer system, or thinking of writing an operating system and tool
chain from scratch.

Building on the 40 years of experience and not reinventing wheels
is the ultimate legacy of the Unix system.










  parent reply	other threads:[~2011-06-28 15:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  0:11 Warren Toomey
2011-06-28  0:26 ` Larry McVoy
2011-06-28  0:32 ` Nick Downing
2011-06-28  1:00 ` Tim Newsham
2011-06-28  3:36 ` Jim Capp
2011-07-02  4:03   ` Warner Losh
2011-08-07 20:26   ` Alan D. Salewski
2011-09-02 18:33     ` Jose R. Valverde
2011-06-28  3:53 ` Jim Capp
2011-06-28  4:13 ` Greg 'groggy' Lehey
2011-06-28  5:48   ` Nick Downing
2011-06-28  7:22     ` Tim Newsham
2011-06-28 14:18   ` Wesley Parish
2011-06-28  7:32 ` Wilko Bulte
2011-06-28 15:22 ` Al Kossow [this message]
2011-06-29  1:30 A. P. Garcia

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=4E09F1B0.90805@bitsavers.org \
    --to=aek@bitsavers.org \
    /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).