The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 17:47:51 -0500	[thread overview]
Message-ID: <20151209224751.GC20697@mercury.ccil.org> (raw)
In-Reply-To: <CAC20D2NcjcA_7NmnuEU-97BrWW3EeDOi51nHzfFr0YZFkG5jPQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

Clem Cole scripsit:

> ​To be fair UNIX was the naming sinner here IMO.  Unix's ld command is the
> "link editor", 

I thought "ld" stood for Link eDitor.  :-)

> I never asked Dennis or Ken why those names were not used.

FWIW, DEC transitioned from "loader" to "link editor".  On OS/8 there
were four linkers, one for each compiler:  ABSLDR, LOAD, LOADER,
and LINK.  LINK was for the macro assembler, the last one published.
I don't remember the story on the various PDP-11 DEC OSes; by VMS days
it was exclusively LINK.  The ABSLDR actually did loading rather than
linking (it was "absolute" in the sense that it did no relocation, so
if parts of your program overwrote other parts, that was your problem).
When it terminated, the executable program was in core (the ABSLDR's
last act was to arrange for the executable to overwrite it) where you
could save it or start it up as you were so minded.

-- 
"Well, I'm back."  --Sam        John Cowan <cowan at ccil.org>



  reply	other threads:[~2015-12-09 22:47 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
2015-12-09 22:47   ` John Cowan [this message]
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=20151209224751.GC20697@mercury.ccil.org \
    --to=cowan@mercury.ccil.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).