The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] changes in C compilers
Date: Sat, 25 Aug 2018 18:19:05 -0400	[thread overview]
Message-ID: <CAC0cEp_HHP93bTksHmb0fTXtwUxagHpSJNC=BypKLViqPArj=w@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PSMD=_RBJ0wYGOSJeZJ=MLLB4yLvJrJjVVteF+GoB9jQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4128 bytes --]

*Ted took fsck back to Summit & MH*

I got my introduction to UNIX in '73 or '74, when the group running the
11/45 in Piscataway found out I came into work before 6am. UNIX was so
unstable back then that it had to be rebooted every day, to contain file
system corruption. A 6 am reboot went pretty much unnoticed. I could swear
we ran something very like fsck after each reboot. In particular, I recall
the **gok** diagnostic when the type of an inode wasn't anything
recognizable. Whatever we ran, I'm sure it continued to evolve.


On Sat, Aug 25, 2018 at 3:58 PM, Clem Cole <clemc@ccc.com> wrote:

>
>
> On Sat, Aug 25, 2018 at 2:38 PM <arnold@skeeve.com> wrote:
>
>> The APS work started in the summer of 1979. See
>> http://www.eprg.org/papers/202paper.pdf
>> and see some of the other stuff at
>> http://www.cs.princeton.edu/~bwk/202/index.html.
>>
>> I think that's after V7 was released.
>>
> Ok, so that was clearly the first ditroff.
>
> Typesetter C *must have been the original troff release* which was
> separate from V6; but I don't remember what all was in the release.
>  Looking at the v6 distribution tape I have, the assembler versions of roff
> and nroff was there; but not troff.   V7 clearly shows the original troff
> in the sources.
>
>
> The order I remember is this ... V5, V6, Patches, Typesetter C, TS, V7
> ...   although TS and Typesetter might be switched but I know we got
> Typesetter C before we got V7.    Ted brought TS to us (in EE) and I
> thought that had the new compiler.   CS got TS from us in EE.    But
> somebody at CMU had wanted troff because we had the XGP in CS that we drive
> with Scribe (I want to say that was EE but I don't remember who was
> involved).   So I have memory of somebody hacking on the compiler at some
> point.  The POR (which if ever came to bear at CMU was after I left) was
> some type of hacking on troff to support the XGP.  Given the time Aharon
> points out, it might have been direct support it or it might have been
> something like vcat - I was not involved.   Klone might remember more of
> that.
>
> Clearly from the time, ditroff did not yet exist.   The more I think about
> it, Brian K actually might know some of the story.  Scribe was Brian Reid's
> PhD Thesis and Brian K was on Reid's committee at the time and I'm guessing
> could somehow have been mixed up.
>
> FWIW: Compiler hacking at CMU stands out in my mind because of the 11/40e
> had CSAV/CRET instructions.  The CS versions of the compilers generated
> code using that, because they had 11/40e with CMU WCS options.  The rest of
> us in EE, BioMed, Mellon Institute etc were running on 11/34's or 11/34A
> which could not handle those binaries (no WCS).   So I personally spent
> time tracking the CS versions of the compiler and bringing things to EE,
> trying to keep thing clean.  That was one of my jobs at the time.
>
> That's fairly sure of the order, because we had Typesetter C at CMU in the
> Summer '78 when were we negotiating the 'university' commercial V7 license
> with Al Arms [which I was personally mixed up -- the finally
> ruling/agreement was license one system as a commercial system at the $20K
> fee and a university, could then use UNIX for back office and commercial
> style uses like Industry.  Al did not require the $5K second CPU stuff from
> the Universities, if they got a single $20K license; everyone was happy -
> details off list or another thread if you want them; although I will say
> CMU was first in early '79, followed by Case in late 1979].
>
> So again, I try to date by things I know are fixed in time and then work
> from there.   As Dan points out the cross pollination was high in those
> days and it was not just from the labs to the Universities.  For instance,
> Ted took fsck back to Summit & MH, as well as a number of other tools
> (although I think that one had the longest reach).   Noel has mentioned
> similar stories from MIT.  Chesson brought all the networking stuff from
> UoI and we saw some of it in datakit (an earlier version of his mpx code
> for V7 he did as a grad student).   You get the idea....
>
> Clem
>
>

[-- Attachment #2: Type: text/html, Size: 7170 bytes --]

  reply	other threads:[~2018-08-25 22:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  7:02 arnold
2018-08-24 12:00 ` Clem cole
2018-08-24 13:50   ` [TUHS] changes in C compilers (Typesetter C) Jaap Akkerhuis
2018-08-25 18:30   ` [TUHS] changes in C compilers arnold
2018-08-25 19:58     ` Clem Cole
2018-08-25 22:19       ` John P. Linderman [this message]
2018-08-25 23:02         ` Clem Cole
2018-08-25 23:14 Noel Chiappa
2018-08-25 23:56 ` Clem Cole
2018-08-30 20:26 Norman Wilson
2018-08-30 20:48 ` Clem Cole

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='CAC0cEp_HHP93bTksHmb0fTXtwUxagHpSJNC=BypKLViqPArj=w@mail.gmail.com' \
    --to=jpl.jpl@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@tuhs.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).