Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Building OS from source in the olden days
Date: Tue, 10 Nov 2020 18:45:15 -0500	[thread overview]
Message-ID: <CAC20D2OA5mqCoHFEg=2+5STe_4mA6DRq=+ofkzbaWS1CsKRXXw@mail.gmail.com> (raw)
In-Reply-To: <20201110231118.GW99027@eureka.lemis.com>

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.   By the time of VMS and the
other minis, you tended to link together from modules, although many sites
did have sources (in assembler).

Remember, the target was the manufacturers HW so they were not giving away
much.   In the case of IBM, eventually, Amdahl started cloning and they got
a tad more closed, but by that time there were also many mainframe OS
flavors in wild.

That said, I think Burrough's gave away the ESPOL code for their systems,
but I never saw it; so I can not speak definitively there.

Unix was different.  Like Burrough's, it was heavily written in a systems
programming language.   To my knowledge, the 'concept' or 'porting' the OS
in it's entirety to a completely new ISA began with UNIX.

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?
>
> 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/ef916116/attachment.htm>


  parent reply	other threads:[~2020-11-10 23:45 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 [this message]
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
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='CAC20D2OA5mqCoHFEg=2+5STe_4mA6DRq=+ofkzbaWS1CsKRXXw@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).