The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Thu, 10 Dec 2015 12:08:18 +1100	[thread overview]
Message-ID: <20151210010818.GE84775@eureka.lemis.com> (raw)
In-Reply-To: <CAC20D2OEOowXDZ3t8WWwPe72bmUkzBjc13Ctk1sMj4kjnAEC_Q@mail.gmail.com>

On Wednesday,  9 December 2015 at 19:23:07 -0500, Clem Cole wrote:
> 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.

My understanding, which predates my contact with Unix, is that the
original toochains for single-job machines consisted of the assembler
or compiler, the output of which was loaded directly into core with
the loader.  As things became more complicated (and slow), it made
sense to store the memory image somewhere on drum, and then load that
image directly when you wanted to run it.  And that in some systems
the name "loader" stuck, even though it no longer loaded.  Something
like the modern ISP use of the term "modem" to mean "router".  But I
don't have anything to back up this version; comments welcome.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151210/fbd67b21/attachment.sig>


  reply	other threads:[~2015-12-10  1:08 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
2015-12-10  1:08       ` Greg 'groggy' Lehey [this message]
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=20151210010818.GE84775@eureka.lemis.com \
    --to=grog@lemis.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).