From: athornton at gmail.com (Adam Thornton)
Subject: [COFF] Building OS from source in the olden days
Date: Tue, 10 Nov 2020 17:10:37 -0700 [thread overview]
Message-ID: <CAP2nic3_-RWfowxqPuu1gyACXeghv4H-+_uBPfXKpdy85xw2_A@mail.gmail.com> (raw)
In-Reply-To: <20201111000621.GY99027@eureka.lemis.com>
Pretty sure this VM/370 reference has, somewhere in its rather formidable
bulk, what you're looking for. Start around p. 225:
http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/370/VM_370/Release_6/GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Now granted VM was never the most popular of the IBM OSes. But it was
delivered (and patched) as assembler sources. You may also enjoy Melinda
Varian's "What Mother Never Told You about VM Service."
http://www.leeandmelindavarian.com/Melinda/tutorial.pdf
On Tue, Nov 10, 2020 at 5:06 PM Greg 'groggy' Lehey <grog at lemis.com> wrote:
> On Tuesday, 10 November 2020 at 18:45:15 -0500, Clem Cole wrote:
> > On Tue, Nov 10, 2020 at 6:11 PM Greg 'groggy' Lehey <grog at lemis.com>
> 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?
> >
> > Mumble -- For IBM and DEC in the 60s and early 70s, the manufactures
> > distributed the (assembler) sources to the OS and we could (and did)
> > build from source but usually just built parts.
>
> Right, this is my recollection.
>
> > Remember, the target was the manufacturers HW so they were not
> > giving away much.
>
> Again, my assessment.
>
> The real issue is: where can I find a reference? Google brings up so
> many false positives that it's not worth the trouble, and Wikipedia's
> pages on "System generation" are too vague.
>
> Greg
> --
> Sent from my desktop computer.
> Finger grog at lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed. If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201110/1de9d07a/attachment.htm>
next prev parent reply other threads:[~2020-11-11 0:10 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 [this message]
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
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=CAP2nic3_-RWfowxqPuu1gyACXeghv4H-+_uBPfXKpdy85xw2_A@mail.gmail.com \
--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).