The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Was pcc ever ported to the CDC6600?
Date: Sat, 21 Jan 2017 23:38:35 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.20.1701212312420.91127@aneurin.horsfall.org> (raw)
In-Reply-To: <c019711a4f34b1fa05b5cafd40dd2dfe4cd04d99@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

On Thu, 19 Jan 2017, Steve Johnson wrote:

> PCC ended up being ported to many dozen different architectures, so it's 
> quite possible, but I don't recall it being done.  It was kind of a 
> dinosaur by the early 70's.  I'm not even sure that it had memory 
> protection, and it certainly didn't have paging.  And the I/O system was 
> strange.  So porting Unix would have been next to impossible.

My memory of the Kyber (as we called them; we had a 72) was that it was 
not character-addressable, but 60-bit word-addressable, thus making string 
handling somewhat difficult.  Don't get me started on its utterly broken 
architecture...  I have thankfully lost my programming manual for the 
beast.

> The main thing I remember about the 6600 was that it didn't have parity 
> bits on its memory.  So people used to run the same program three times 
> and if two of the answers agreed, they published...

Parity only slowed it down, and besides, hardware never failed...

My fondest memory of the thing was its command completion; I would start 
to type "O, TR" and it would fill out "O, TRANSACTION TERMINAL STATUS".  
Which reminds me that my worst memory was its console keyboard, with "0"
on the left...
 
-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."


  parent reply	other threads:[~2017-01-21 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19  2:52 Nemo
2017-01-19 17:47 ` Steve Johnson
2017-01-19 17:52   ` ron minnich
2017-01-19 18:06   ` Charles Anthony
2017-01-21 12:38   ` Dave Horsfall [this message]
2017-01-21 12:51     ` Kay Parker   
2017-01-21 14:42       ` Lorne Wilkinson
2017-01-21 15:44         ` Larry McVoy
2017-01-21 22:55       ` Dave Horsfall
2017-01-21 16:27     ` Ronald Natalie

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=alpine.BSF.2.20.1701212312420.91127@aneurin.horsfall.org \
    --to=dave@horsfall.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).