From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the SGS (System Generation Software) and COFF (Common Object File Format)
Date: Sat, 25 Feb 2023 13:07:01 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2302251302070.56283@aneurin.horsfall.org> (raw)
In-Reply-To: <CABH=_VRWFcpSPuC3CL9K5XO9AEYnOucV4k5+rp=koTEjn-RSFA@mail.gmail.com>
On Thu, 23 Feb 2023, Paul Winalski wrote:
> a.out was, as object file formats go, a throwback to the stone age from
> the get-go. Even the most primitive of IBM's link editors for
> System/360 supported arbitrary naming of object file sections and the
> ability for the programmer to arrange them in whatever order they
> wished. a.out's restriction to three sections (.text, .data, .bss) did
> manage to get the job done, and even (with ZMAGIC) could support
> demand-paged virtual memory, but only just.
That may be so, but those guys didn't exactly have the resources of
IBM behind them...
And I wonder how many people here know the significance of the "407" magic
number?
-- Dave
next prev parent reply other threads:[~2023-02-25 2:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:16 [TUHS] " segaloco via TUHS
2023-02-22 22:20 ` [TUHS] " Clem Cole
2023-02-23 0:17 ` segaloco via TUHS
2023-02-23 6:30 ` Lars Brinkhoff
2023-02-23 14:25 ` KenUnix
2023-02-23 19:37 ` Warner Losh
2023-02-24 17:01 ` Rich Salz
2023-02-23 16:49 ` Paul Winalski
2023-02-23 18:38 ` segaloco via TUHS
2023-02-23 20:40 ` Paul Winalski
2023-02-24 12:45 ` arnold
2023-02-24 13:13 ` Arno Griffioen via TUHS
2023-02-25 19:28 ` arnold
2023-02-25 19:34 ` Steffen Nurpmeso
2023-02-24 14:01 ` Harald Arnesen
2023-02-25 2:07 ` Dave Horsfall [this message]
2023-02-25 15:30 ` Clem Cole
2023-02-25 17:29 ` Paul Winalski
2023-02-23 15:13 Noel Chiappa
2023-02-23 21:37 Paul Ruizendaal
2023-02-23 22:11 ` segaloco via TUHS
2023-02-24 0:07 ` segaloco via TUHS
2023-02-25 20:14 Brian Walden
2023-02-26 15:51 Paul Winalski
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=alpine.BSF.2.21.9999.2302251302070.56283@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=tuhs@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).