From: Clem Cole <clemc@ccc.com>
To: Michael Casadevall <michael@casadevall.pro>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code
Date: Mon, 10 Oct 2022 17:37:00 -0400 [thread overview]
Message-ID: <CAC20D2OUwYEBMDBk80Ngnojmb=on_ArHHF78m3tHe8tSd0XsAw@mail.gmail.com> (raw)
In-Reply-To: <CAEMRDeEFgu5P1f49Q6h9vR3cM62yH7XEjYn1ujOLR4E1Yfmbnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3270 bytes --]
On Mon, Oct 10, 2022 at 4:49 PM Michael Casadevall <michael@casadevall.pro>
wrote:
>
> There are SCCS references in the code from 78/79, references to the V7 CC
> compiler and updates.
>
The 'V7 compiler' is 'Typesetter C' - it was released two compiler DWB on
V6.
SCCS had a interesting life.
> SCCS was introduced publicly with PWB,
>
Indeed.
> which is why I suspect it might have been used.
>
It might have been at MIT (it was a UCB and CMU BTW) - but I believe Al
Nemeth - while it might have been a person disk, -- I'm pretty sure BBN
would have tried to kept those bits out of the building. - certainly out of
the mainstream of any project -- you see in the directories foo.c and
foo.c~ files -- this was typical of the day. If you were using SCCS less
you would see a lot more evidence in the trees (again look at the UCB trees
- you can see once Ken brought it to UCB, wnj started to use it).
> The code also uses some C syntax the stock compiler dislikes
> (specifically, it was unhappy register in the function declaration).
>
As I said -- I suspect the typesetter compiler by then. If userspace code
is using <stdio.h> and linking libS.a not Mike Lesk's portable I/O
library that's a huge clue also BTW. But Dennis did a lot of work to the
compiler in the DWB timeframe. A number of language features were added,
he changed the syntax of things like =+ to += and the like. This is why
code that targets the Typesetter C compiler has a very difficult time going
back to the V6 (or basic PWB 1.0) compilers. As I said in the other
message, this was the compiler he and Brian describe in the book - also
note a couple of us here reviewed different editions of it.
I suspect what you need is the original DWB 1.0 release that includes the
'typesetter' compiler -- that will bootstrap on a V6 system and will create
a v6 compiler. I'm not sure we have that in the archives. I think we have
the later PWB 2.0 release - that comes without the compiler.
Beside the startup code (which is in mch.c and uses a preprocessor macro),
> is there anything specific gotchas in regards to models? I tried building
> CPU40 and CPU70, and configuring simh, just to eliminate that gotcha, but
> the only difference seems to be early initialization code ...
>
Quick glance is that BBN was running a 45 - so I'd build for that to
start. 45s and 70s's are more similar but not exactly the same. Don't
build for a 40. They are quite different.
Set simh up as a 45 and see if that just works.
If not .... then I would drop back and pull everything out to as simple a
UNIX as possible... since it's a v6 system without any of the networking
-- as much line Ken and Dennis as you can. Configure that a 40 and follow
Dennis's and Ken's instructions (which for v6 is a a 40) -- get that to
boot and a simh based 40. Then reconfigure as a simh based 45 and make
that work. Then and only then turn on the BBN stuff.
Feel free to send me email off line and I can try to help a little. Note:
I have not played with a 45 in years. But I ran V5, V6. and V7 on 40s, 45
and 70s back in the day. I have a PiDP 11/70 behind me so modulo being way
to busy, I can try to help a little.
ᐧ
[-- Attachment #2: Type: text/html, Size: 6598 bytes --]
next prev parent reply other threads:[~2022-10-10 21:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 18:33 [TUHS] " Michael Casadevall
2022-10-10 19:48 ` [TUHS] " Lars Brinkhoff
2022-10-10 20:31 ` Michael Casadevall
2022-10-11 5:31 ` Lars Brinkhoff
2022-10-11 12:57 ` Michael Casadevall
2022-10-11 13:57 ` Lars Brinkhoff
[not found] ` <CAJq=PCV7o_kMvRLXXK9prddmyvf0hAodX+NuqqVF=49iCYt63w@mail.gmail.com>
2022-10-11 19:58 ` Lars Brinkhoff
2022-10-10 20:31 ` Clem Cole
2022-10-10 20:48 ` Michael Casadevall
2022-10-10 21:37 ` Clem Cole [this message]
2022-10-11 15:08 Paul Ruizendaal
2022-10-12 19:38 Noel Chiappa
2022-10-13 5:50 ` Lars Brinkhoff
2022-10-14 11:55 Paul Ruizendaal
2022-10-14 16:08 ` Phil Budne
2022-10-14 16:37 ` Clem Cole
2022-10-14 19:06 ` Warner Losh
2022-10-14 18:47 ` Lars Brinkhoff
2022-10-14 20:30 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='CAC20D2OUwYEBMDBk80Ngnojmb=on_ArHHF78m3tHe8tSd0XsAw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=michael@casadevall.pro \
--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).