From: Rich Salz <rich.salz@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Origins of the SGS (System Generation Software) and COFF (Common Object File Format)
Date: Fri, 24 Feb 2023 12:01:28 -0500 [thread overview]
Message-ID: <CAFH29tqUiFGfApyAv140ZH8MYYDCgCfrY4m8UHOAZ3Ns6tH6_Q@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrjLur0mnq4YtyXERkH4X-Utf3_ZF4TBY3hno4R=vrc1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
> MIT's PCC ports to various micros, especailly x86, also used b.out that
> was quite similar to a.out.
>
That was a cross-compiler, right? If so, I remember going over to MIT-LCS
and picking up a copy of the sources for the compiler and the MIT PC/IP
implementation. I had to show a copy of my ATT source license to the
secretary, who made a copy of a 9track tape for me.She was a hoot: dressed
like a punk, and we takled about not working for defense companies. We were
then able to build and install various TCP/IP utilities on our PC-AT
machines running early Windows releases. This was probably early 1980's. I
think the PC/IP code was based on David Clark's upcalls idea[1]. It later
became the basis for FTP software, which then died when Microsoft added TCP
to windows.
[1]
https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=e7c6da568d15a3ea50854dbd951c1d6394502a15
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
next prev parent reply other threads:[~2023-02-24 17:01 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 [this message]
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=CAFH29tqUiFGfApyAv140ZH8MYYDCgCfrY4m8UHOAZ3Ns6tH6_Q@mail.gmail.com \
--to=rich.salz@gmail.com \
--cc=imp@bsdimp.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).