Computer Old Farts Forum
 help / color / mirror / Atom feed
From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] Building OS from source in the olden days
Date: Wed, 11 Nov 2020 11:02:58 +1100	[thread overview]
Message-ID: <20201111000258.GX99027@eureka.lemis.com> (raw)
In-Reply-To: <CAP2nic0LCUEGmMJ6_3OJQw8UPZgozjJGoetHJabL-w0DFL6neg@mail.gmail.com>

On Tuesday, 10 November 2020 at 16:52:58 -0700, Adam Thornton wrote:
> If 4.3BSD is old enough, the System Administrator's Manual (e.g.
> http://bitsavers.informatik.uni-stuttgart.de/pdf/isi/bsd/490197C_Unix_4.3BSD_System_Administrator_Guide_ISI_Release_4.1_May88.pdf)
> section 4.2 _et seq_.
>
> On Tue, Nov 10, 2020 at 4: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?
>
> How olden days do you mean?

Sorry, I wasn't very clear.  I was thinking commercial systems of the
1960s and 1970s, not any form of Unix.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201111/599d84c8/attachment.sig>


  parent reply	other threads:[~2020-11-11  0:02 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 [this message]
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=20201111000258.GX99027@eureka.lemis.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).