The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: segaloco <segaloco@protonmail.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the SGS (System Generation Software) and COFF (Common Object File Format)
Date: Thu, 23 Feb 2023 12:37:33 -0700	[thread overview]
Message-ID: <CANCZdfrjLur0mnq4YtyXERkH4X-Utf3_ZF4TBY3hno4R=vrc1g@mail.gmail.com> (raw)
In-Reply-To: <7wcz60x5ae.fsf@junk.nocrew.org>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Wed, Feb 22, 2023 at 11:30 PM Lars Brinkhoff <lars@nocrew.org> wrote:

> Clem Cole wrote:
> > MIT had a modified a.out format for the NU machine ports - that might
> > have been called b.out.  CMU had macho which again was an extended
> > a.out but even more flexible.
>
> Digital Research's GEMDOS also used a modified a.out format (at least as
> found on the Atari ST), pretty much the original PDP-11 format with
> 32-bit addresses.
>

MIT's PCC ports to various micros, especailly x86, also used b.out that was
quite similar to a.out.

Warner

[-- Attachment #2: Type: text/html, Size: 941 bytes --]

  parent reply	other threads:[~2023-02-23 19:37 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 [this message]
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
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='CANCZdfrjLur0mnq4YtyXERkH4X-Utf3_ZF4TBY3hno4R=vrc1g@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=lars@nocrew.org \
    --cc=segaloco@protonmail.com \
    --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).