From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] Building OS from source in the olden days
Date: Wed, 11 Nov 2020 14:09:51 +1100 [thread overview]
Message-ID: <20201111030951.GD99027@eureka.lemis.com> (raw)
In-Reply-To: <CAP2nic24WCWz0A=W6Z5Ez_NJzLrDrQKWcZChQ-+T9xzg6n4cFA@mail.gmail.com>
On Tuesday, 10 November 2020 at 17:12:27 -0700, Adam Thornton wrote:
> I don't know enough about MVS but it too is public domain until 3.8j or so,
> and I would expect that the way you serviced the system was about the same:
> patch the assembly code from PTFs (or whatever those are called in
> MVS-land),
Right! There's a TLA that rings a bell. "Permanent Temporary Fix"?
Or was that a reinterpretation? But yes, it's clearly source-related.
> reassemble the modules, relink into a kernel/system image/whatever
> the os-appropriate nomenclature is.
Yup. That reminds me of a poem published in Datamation decades ago:
On either die the printer lie
Fat stacks of paper six feet high
That stun the mind abnd blur the eye,
And lo! Still more comes streaming by,
A fresh SYSABEND dump.
Ye printer clackth merrily
"Compleccioun code is 043"
Alack! What can the matter be
That made SYSABEND dump?
My TCAM hath no MCP?
My data cannot OPENed be?
Consult my neighbourhood SE?
The devil take thy dam and thee,
Thou vile SYSABEND dump!
Assemble modules on the fly
And link for yet another try.
With SUPERZAP a patch apply,
This time THOU SHALT NOT DUMP!
On either side the printer lie
Fat stacks of paper twelve feet high
That blow the mind and blast the eye.
Gadzooks! How shrill yon varlet's cry
As sixteen megabytes go by
In yet another dump.
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/fc5d54c8/attachment.sig>
next prev parent reply other threads:[~2020-11-11 3:09 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 [this message]
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=20201111030951.GD99027@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).