The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] [TUHS} PDP-11, Unix, octal?
Date: Wed, 18 Jan 2017 11:47:05 -0500	[thread overview]
Message-ID: <CAC20D2PazhnOeekdPPavtzCr2AV2HOw5pqk-TR9ZDY3RqVJLuA@mail.gmail.com> (raw)
In-Reply-To: <201701170223.v0H2N7Q9010667@coolidge.cs.Dartmouth.EDU>

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

On Mon, Jan 16, 2017 at 9:23 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:

> ctal was reinforced by a decade of 6-bit bytes.
> Perhaps the real question is why did IBM break so completely to hex
> for the 360?
>
​I may be able to help a little here.  A few years ago I used work with
Russ Robelen who was the Chief Designer of the 360/50​.   Russ regaled us
with a number of the stories from those times and having met a few of the
personalities involved in them I tend to believe Russ's stories as I have
heard other of similar color.

The first important thing about the 360 was it was supposed to be an the
first ASCII machine from IBM.   It's funny how history would use prove it
otherwise, but IBM had invested heavily and originally planned on going
ASCII.   And the key is that ASCII was originally a 7-bit character set,
being able to store a 7 bit character was an important design idea for the
architecture.

According to Russ, Amdahl came up with some [IMO hokey] schemes (similar to
what CDC would do) that mapped into 6 bits.  I understand that he even
proposed a 7-bit byte.   He felt that 8 bits was wasteful of the hardware.
Russ says that, Brooks would toss him out of his office and said something
on the order don't come back until you have a power of 2 - that he (Brooks)
did not know how to program things in multiples of 3 and things made of 7s
were ever worse.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170118/288fcf7c/attachment.html>


  reply	other threads:[~2017-01-18 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  2:23 Doug McIlroy
2017-01-18 16:47 ` Clem Cole [this message]
2017-01-18  2:33 Noel Chiappa
2017-01-18  3:06 ` Steve Johnson
2017-01-18  3:36   ` Dan Cross
2017-01-18  6:53     ` Angelo Papenhoff
2017-01-18  7:31       ` ron minnich
2017-01-18  8:09         ` Angelo Papenhoff
2017-01-18 21:04     ` Steve Johnson
2017-01-18 21:42       ` Charles Anthony
2017-01-18  6:04   ` Lars Brinkhoff
2017-01-18 18:47     ` Peter Jeremy
2017-01-18 18:58       ` Charles Anthony
2017-01-18 14:28 Nelson H. F. Beebe

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=CAC20D2PazhnOeekdPPavtzCr2AV2HOw5pqk-TR9ZDY3RqVJLuA@mail.gmail.com \
    --to=clemc@ccc.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).