Computer Old Farts Forum
 help / color / mirror / Atom feed
From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] Building OS from source in the olden days
Date: Wed, 11 Nov 2020 12:01:40 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2011111133190.48674@aneurin.horsfall.org> (raw)
In-Reply-To: <20201110231118.GW99027@eureka.lemis.com>

On Wed, 11 Nov 2020, Greg 'groggy' Lehey wrote:

> I'm currently reviewing a paper about Unix and Linux, and I made the 
> comment that in the olden days the normal way to build an OS image for a 
> big computer was from source.  Now I've been asked for a reference, and 
> I can't find one!  Can anybody help?

Depends what you mean by "olden days" and "big computer".  As I recall we 
(Uni of NSW) had the source to the 360/50 and the Cyber 72, but not for 
the VMS stuff; binaries were patched with IEBUPDTE and later on SUPERZAP 
(possibly written locally).

I got an official pat on the back for getting SPITBOL to work after its 
time-bombs (yes, plural) expired[*]...

And we had the source to something called Unix Edition 5 & 6 etc, but they 
were hardly mainframes :-)

[*]
The first bomb failed with an error message, so I patched that.  It then 
started crashing rather mysteriously, and I discovered that it was taking 
an indirect jump to whatever was in R0 at the time (I think).  Rather than 
waste time digging them all out, I wrote a program that LOADed the binary, 
scanned memory for a word that matched that date, and printed each address 
so they could then be inspected by hand.  There were something like six of 
them...  One big SUPERZAP later, and we had a working SPITBOL compiler 
again; a bored CompSci student is terrible to behold.

-- Dave


  parent reply	other threads:[~2020-11-11  1:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 23:11 grog
2020-11-10 23:38 ` imp
2020-11-10 23:45 ` clemc
2020-11-11  0:06   ` grog
2020-11-11  0:10     ` athornton
2020-11-11  0:12       ` athornton
2020-11-11  3:09         ` grog
2020-11-11  4:54           ` dave
2020-11-11  4:58             ` grog
2020-11-13  2:15               ` dave
2020-11-13  6:57                 ` athornton
2020-11-11  2:07     ` clemc
2020-11-11  0:01 ` bakul
2020-11-11  1:26   ` dave
     [not found] ` <CAP2nic0LCUEGmMJ6_3OJQw8UPZgozjJGoetHJabL-w0DFL6neg@mail.gmail.com>
2020-11-11  0:02   ` grog
2020-11-11  1:01 ` dave [this message]
2020-11-11  2:03   ` brad
2020-11-11  3:11   ` grog
2020-11-11  3:22     ` athornton
2020-11-11  5:15     ` dave

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=alpine.BSF.2.21.9999.2011111133190.48674@aneurin.horsfall.org \
    --to=coff@minnie.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).