From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 19:23:07 -0500 [thread overview]
Message-ID: <CAC20D2OEOowXDZ3t8WWwPe72bmUkzBjc13Ctk1sMj4kjnAEC_Q@mail.gmail.com> (raw)
In-Reply-To: <20151209224751.GC20697@mercury.ccil.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Wed, Dec 9, 2015 at 5:47 PM, John Cowan <cowan at mercury.ccil.org> wrote:
> I thought "ld" stood for Link eDitor. :-)
>
I have never heard that justification. It's always been talked about as
the "loader" communications I had with different folks including Dennis.
In the early/mid '70s the person that introduced me to Unix (tjk) always
called it the loader. Ted was (like many of us in those days) coming
from either IBM's TSS or MTS, and influenced by IBM's terminology as well
as DECs.
> 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 used TSS/8 and I've forgotten what is was called there, never used
OS/8. In TOPS and Tenex land it was called a linker, as it was on TSS and
MTS.
> I don't remember the story on the various PDP-11 DEC OSes;
>
RT-11, DOS-11 and RSX all called it a linker.
> by VMS days
>
> it was exclusively LINK.
>
As the author of VMS's link and later versions, I'll try to ask Paul
tomorrow what he knows/remembers. In my presence, he has b*tched about
Unix calling it a 'loader.
'
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151209/0fcdd1f3/attachment.html>
next prev parent reply other threads:[~2015-12-10 0:23 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
2015-12-09 23:39 ` Steve Nickolas
2015-12-10 0:24 ` Clem Cole
2015-12-10 0:23 ` Clem Cole [this message]
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=CAC20D2OEOowXDZ3t8WWwPe72bmUkzBjc13Ctk1sMj4kjnAEC_Q@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).