From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] PDP-10 UNIX?
Date: Mon, 18 Sep 2017 12:42:02 -0400 [thread overview]
Message-ID: <ca241180-8031-f1d4-1d8f-382620ff2c4c@kilonet.net> (raw)
In-Reply-To: <CAC20D2O1_qteChioos=Kgt0aq1YCxpbNR7eAHW1PUWqox=LUKQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
The MACRO-10 assembler used a keyword ASCIIZ to store that
7-bit/1-bit-wasted ASCII format.
MOVEI 0,[ASCIIZ /Hello there
/]
for example. It was the defacto standard for null-terminated ASCII strings.
When I later moved to C on 8/16-bit computers, I remember thinking
"what's with this signed 8-bit char thing?" ;)
There was also SIXBIT - almost everything ASCII had, but only upper
case. The filesystem used that for filenames and extensions, and it was
used in a few other areas. So any library calls like open() would have
had to convert the ASCII filename to SIXBIT before doing any monitor calls.
On 9/18/2017 9:50 AM, Clem Cole wrote:
>
>
> On Sun, Sep 17, 2017 at 11:22 AM, Arthur Krewat <krewat at kilonet.net
> <mailto:krewat at kilonet.net>> wrote:
>
> I have a C compiler for TOPS-10 that I got off the Internet back
> in 1988. Still haven't messed around with it enough to get it to
> run, but ...
>
> There was a PDP-10 C compiler in the late 1970s, that was kicking
> around CMU, MIT and Stanford which we used to write backup10 and and
> an implementation of tar. IIRC, it was based on the the Ritchie
> front end and was V6 in syntax (i.e. pre-V7 or typesetter C - aka
> 'White Book). I've forgotten the rules of chars, but I remember you
> had to be careful. I think it was 4 9-bit chars to transfer things
> (4*9=36 bits), but I think I remember there were cases on output that
> it wanted to wash it through a 7-bit PDP-10 char (5*7+1 =36bits) which
> was the 'norm' for most languages like SAIL, BLISS et al.
>
> I did not mess with much, but that time, I was transitioning from the
> 10's to UNIX by that time. I added support for the -20's dumper
> tapes to backup10 which were almost but not quite the same. But that
> was the last I messed with it. Mike Accetta and Fil Aliva (of CMU Mach
> fame) I remember had their had in that subsystem, at one point. And
> of course Danny Klein is always a good one from those days to ask too.
> I'll see if I can dig them up and ask.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170918/26ad8ccd/attachment.html>
next prev parent reply other threads:[~2017-09-18 16:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 14:28 Arthur Krewat
2017-09-17 14:31 ` Warner Losh
2017-09-17 15:01 ` Lars Brinkhoff
2017-09-17 15:22 ` Arthur Krewat
2017-09-18 13:50 ` Clem Cole
2017-09-18 16:42 ` Arthur Krewat [this message]
2017-09-18 19:58 ` Lars Brinkhoff
2017-09-18 20:10 ` Clem Cole
2017-09-18 20:22 ` Lars Brinkhoff
2017-09-18 20:43 ` Clem cole
2017-09-19 9:06 ` Mutiny
2017-09-19 9:56 ` Lars Brinkhoff
2017-09-17 16:33 ` Warner Losh
[not found] <mailman.1031.1505666037.3779.tuhs@minnie.tuhs.org>
2017-09-18 2:34 ` Johnny Billquist
2017-09-18 15:30 ` Arthur Krewat
2017-09-18 16:46 ` Steve Johnson
2017-09-18 17:25 ` Clem Cole
2017-09-18 17:40 ` Larry McVoy
2017-09-18 20:08 ` Chris Torek
2017-09-18 17:24 Nelson H. F. Beebe
2017-09-18 18:10 ` Lars Brinkhoff
2017-09-20 4:55 ` Warner Losh
2017-09-18 21:14 Noel Chiappa
2017-09-19 6:46 ` Lars Brinkhoff
2017-09-20 18:40 Nelson H. F. Beebe
2017-09-24 18:29 ` arnold
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=ca241180-8031-f1d4-1d8f-382620ff2c4c@kilonet.net \
--to=krewat@kilonet.net \
/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).