Computer Old Farts Forum
 help / color / mirror / Atom feed
From: athornton at gmail.com (Adam Thornton)
Subject: [COFF] Building OS from source in the olden days
Date: Thu, 12 Nov 2020 23:57:11 -0700	[thread overview]
Message-ID: <CAP2nic2rz21rsJhyfrM09t9cM0Sb5r108SkgJreJKdZLpGkz=w@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2011131309290.48674@aneurin.horsfall.org>

This has inspired me to re-read Melinda Varian's "What Mother Never Told
You About VM Service" and it's still a magnificent document.  I once again
find the control files confusing as hell, but once you get used to how they
work, which once upon a time I was, you had a repeatable (and unwindable!)
service process.

I miss the casualness with which you'd build a new CP nucleus and test it
out on a second-level system.  It's so much better than anything in the
Unix world, far more elegant than testing kernel patches in a Linux virtual
machine, largely because of the ease with which you can attach minidisks to
a first, second, or whatever-level system.  I guess cgroups and bind mounts
finally get you most of the way there in terms of mounting arbitrary
storage to virtual systems, but it's still a pain in the ass to test
multiple kernels.

Not that I spend much time anymore that far down in the system (any
system!), but...VM got a lot of things right.

Adam

On Thu, Nov 12, 2020 at 7:15 PM Dave Horsfall <dave at horsfall.org> wrote:

> On Wed, 11 Nov 2020, Greg 'groggy' Lehey wrote:
>
> >> Program Temporary Fix.
> >
> > Yes.  But I recall correctly.  See the Wikipedia page:
> >
> >  Customers sometimes explain the acronym in a tongue-in-cheek manner as
> >  permanent temporary fix or more practically probably this fixes,
> >  because they have the option to make the PTF a permanent part of the
> >  operating system if the patch fixes the problem.
>
> Yeah, they did have a habit of being permanent, but I don't recall
> them ever being called by any of those names during my servitude.
>
> -- Dave
> _______________________________________________
> 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/20201112/b57a2bd0/attachment.htm>


  reply	other threads:[~2020-11-13  6:57 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 [this message]
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='CAP2nic2rz21rsJhyfrM09t9cM0Sb5r108SkgJreJKdZLpGkz=w@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).