From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Don't know much about history
Date: Wed, 30 Jun 2004 00:58:54 -0700 [thread overview]
Message-ID: <f78e33ac6ab2511fcb04443727e4406a@collyer.net> (raw)
In-Reply-To: <85f02f6cb97f9c7eaa11ea22b81d91d2@9netics.com>
Amdahl's machines were called 470s and their front-end communications
processors were called 4705s, if memory serves. Their initial Unix
was called something like UTS/370 (I'm sure about the `UTS' part). We
ran several virtual machines of UTS on an IBM 3033 that IBM donated,
for undergraduate use at U of Toronto in the early 1980s. UTS was a
port of V7, with a few gratuitous C library interface changes, a port
of dmr's V6 PDP-11 C compiler, and no fsck. Their fsck replacement
had the charming property that it only worked on file systems with a
handful of errors needing repair, so just when you really needed it,
it gave up. I ported V7's fsck quickly and we used that instead. The
system used ASCII internally and translated to and from EBCDIC where
necessary at the edges (some terminal I/O, printing, etc.). It had
support for VM/370's virtual card readers, card punches and line
printers, so inter-virtual-machine communication was done via virtual
card images. At the time, it seemed really fast. It could fsck an
entire 3330 disk drive in 30 seconds. `make' and `make -n' ran at
about the same speed. Its Achille's heel was that IBM machines tended
to have operators, who thought they could just `force down' (crash)
virtual machines running UTS, though we told them over and over that
they needed to shut them down gracefully, including syncing them, and
provided them with a simple way to do so.
I'm pretty sure that UTS (d)evolved and become System V.something.
Google is unreachable now (as is much of the Internet), but I think
the Wollongong Group were best known for Eunice, a Unix emulator that
ran (slowly) on VAX/VMS.
next prev parent reply other threads:[~2004-06-30 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 5:20 Jack Johnson
2004-06-30 7:12 ` Skip Tavakkolian
2004-06-30 7:26 ` Richard Miller
2004-06-30 21:34 ` boyd, rounin
2004-07-01 3:57 ` Geoff Collyer
2004-06-30 7:48 ` Richard Miller
2004-06-30 21:16 ` boyd, rounin
2004-06-30 7:57 ` Richard Miller
2004-06-30 7:58 ` Geoff Collyer [this message]
2004-06-30 8:35 ` George Michaelson
2004-06-30 21:29 ` boyd, rounin
2004-06-30 21:22 ` boyd, rounin
2004-06-30 21:15 ` boyd, rounin
2004-06-30 8:46 ` Steve Simon
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=f78e33ac6ab2511fcb04443727e4406a@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).