From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 17:31:00 -0500 [thread overview]
Message-ID: <CAC20D2NcjcA_7NmnuEU-97BrWW3EeDOi51nHzfFr0YZFkG5jPQ@mail.gmail.com> (raw)
In-Reply-To: <20151209221624.B27CC18C0C9@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Wed, Dec 9, 2015 at 5:16 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
>
>
> Actually, it's read by the exec() system call (in sys1.c).
>
>
To be fair UNIX was the naming sinner here IMO. Unix's ld command is the
"link editor", and exec(2) is the "program loader" in the pure OS/academic
naming sense. I never asked Dennis or Ken why those names were not used.
I suspect like creat(2) it made sense at the time and then by the time the
functions leveled out, it was embedded too deep the change it.
BTW: the DEC (vms) link editor runs on Ultrix (PDP-11 and Vaxen). The
binaries are part of the Fortran kit. I'm not sure if it will run on V7
but it might work on BSD 2.x. It's author sits a few feet from me these
days. When DEC finally went to support DEC standard Fortran on UNIX it
was just easier to make the VMS link know how to output an a.out (and macho
files) and the end, then it was to try to add the features they needed for
Fortran to ld and a.out.
It's interesting hearing from Paul his issues over the years between, Unix,
NT, Apple etc., a.out, COFF, and other formats.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151209/559b62b8/attachment.html>
next prev parent reply other threads:[~2015-12-09 22:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 22:16 Noel Chiappa
2015-12-09 22:31 ` Clem Cole [this message]
2015-12-09 22:47 ` John Cowan
2015-12-09 23:39 ` Steve Nickolas
2015-12-10 0:24 ` Clem Cole
2015-12-10 0:23 ` Clem Cole
2015-12-10 1:08 ` Greg 'groggy' Lehey
2015-12-10 9:42 ` Jacob Ritorto
2015-12-10 1:19 ` John Cowan
2015-12-10 10:06 ` Oliver Lehmann
2015-12-10 19:50 ` Will Senn
-- strict thread matches above, loose matches on Subject: below --
2015-12-19 13:27 Noel Chiappa
2015-12-10 4:50 Noel Chiappa
2015-12-09 22:01 Noel Chiappa
2015-12-09 17:50 Noel Chiappa
2015-12-09 18:06 ` Will Senn
2015-12-09 14:56 Noel Chiappa
2015-12-09 16:37 ` Will Senn
2015-12-09 14:24 Noel Chiappa
2015-12-09 13:30 Noel Chiappa
2015-12-09 14:43 ` Ronald Natalie
2015-12-09 20:41 ` Dave Horsfall
2015-12-09 5:17 Noel Chiappa
2015-12-09 5:55 ` Mark Longridge
2015-12-09 11:31 ` Ronald Natalie
2015-12-09 4:53 Noel Chiappa
2015-12-09 14:38 ` Will Senn
2015-12-09 14:56 ` Clem Cole
2015-12-09 15:07 ` Clem Cole
2015-12-09 16:29 ` Will Senn
2015-12-09 14:59 ` Hellwig Geisse
2015-12-09 17:55 ` Will Senn
2015-12-09 3:33 Will Senn
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=CAC20D2NcjcA_7NmnuEU-97BrWW3EeDOi51nHzfFr0YZFkG5jPQ@mail.gmail.com \
--to=clemc@ccc.com \
/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).