The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: beebe@math.utah.edu (Nelson H. F. Beebe)
Subject: [TUHS] PDP-11, Unix, octal?
Date: Tue, 17 Jan 2017 08:14:51 -0700	[thread overview]
Message-ID: <CMM.0.96.0.1484666091.beebe@gamma.math.utah.edu> (raw)
In-Reply-To: <587e2a1e.bls9D6AZ7WMsQuDc%schily@schily.net>

Joerg Schilling asks today:

>> this has been done with 10 6 bit chars in a 60 bit word.
>> Did people use octal in this area?

I worked on a CDC 6400 with both NOS and KRONOS operating systems in
the 1970s.  The 6400/6600/7600 family were definitely in the octal
world.  Initially, the character set was 6-bit, with one character
reserved as an escape to mean that the next 6-bit chunk was to be
included, giving a 12-bit representation that added support for
lowercase letters (a feature that we could only get on our IBM 360 and
Amdahl 470 mainframes with a once-a-night change of the line printer
glyph chain).

Here is a quote by the lead architect, James E. Thornton, who wrote
the 1970 book, ``Design of a Computer: the Control Data 6600'', and
the 1980 history paper ``The CDC 6600 Project''
(http://dx.doi.org/10.1109/MAHC.1980.10044):

>> The selection of 60-bit word length came after a lengthy
>> investigation into the possibility of 64 bits.  Without going
>> into it in depth, our octal background got the upper hand.

That comes from page 347 of the paper.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe at math.utah.edu  -
- 155 S 1400 E RM 233                       beebe at acm.org  beebe at computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------


  reply	other threads:[~2017-01-17 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:10 [TUHS] Article on 'not meant to understand this' Steve Johnson
2017-01-16 20:15 ` [TUHS] PDP-11, Unix, octal? Warren Toomey
2017-01-16 20:25   ` Lars Brinkhoff
2017-01-16 22:31     ` ron minnich
2017-01-16 20:31   ` Erik E. Fair
2017-01-17  1:09   ` Steve Johnson
2017-01-17  1:33     ` William Pechter
2017-01-17 14:28     ` Joerg Schilling
2017-01-17 15:14       ` Nelson H. F. Beebe [this message]
2017-01-17 16:53         ` William Cheswick
2017-01-17 14:12   ` Joerg Schilling
2017-01-17 15:28     ` ron minnich
2017-01-16 20:45 Noel Chiappa

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=CMM.0.96.0.1484666091.beebe@gamma.math.utah.edu \
    --to=beebe@math.utah.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).