The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 21:37:40 -0400 (EDT)	[thread overview]
Message-ID: <21D1C841C4310FE1829023B424252295.for-standards-violators@oclsc.org> (raw)

Clem Cole:

> Apologies to TUHS - other than please don't think Fortran did not
> impact UNIX and its peers.

Fortran had an important (if indirect) influence in early Unix.  From
Dennis's memories of the early days of Unix on the PDP-7:

  Soon after TMG became available, Thompson decided that we could not
  pretend to offer a real computing service without Fortran, so he sat
  down to write a Fortran in TMG.  As I recall, the intent to handle
  Fortran lasted about a week.  What he produced instead was a definition
  of and a compiler for the new language B.

(The Evolution of the Unix Time-Sharing System; see the 1984
UNIX System issue of the BLTJ for the whole thing, or just read
https://www.bell-labs.com/usr/dmr/www/hist.html)

Now let's move on to the name `rc'.  Not the shell, but the
usage as part of a file name.  Those two characters appear
at the end of the many annoying, and mostly pointless, configuration
files that litter one's home directory these days, apparently
copied from the old system-startup script /etc/rc as if the
name means `startup commands' (or something beginning with r,
I suppose, instead of startup).  But I recall reading somewhere
that it just stood for `runcom,' a Multics-derived term for what
we now call a shell script.

I can't find a citation to back up that claim, though.  Anyone
else remember where to look?

Norman Wilson
Toronto ON


             reply	other threads:[~2023-06-13  1:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  1:37 Norman Wilson [this message]
2023-06-13  1:41 ` Rob Pike
2023-06-13  1:48 ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2023-06-13 12:10 Douglas McIlroy
2023-06-13 10:03 Rudi Blom
2023-06-13  0:46 Douglas McIlroy
2023-06-12 18:22 [TUHS] " ron minnich
2023-06-12 18:29 ` [TUHS] " Dan Cross
2023-06-12 18:53   ` Clem Cole
2023-06-12 19:45     ` segaloco via TUHS
2023-06-12 20:03       ` Chris Pinnock via TUHS
2023-06-12 20:22         ` Dan Cross
2023-06-12 20:28           ` Chris Pinnock via TUHS
2023-06-12 20:58             ` Paul Winalski
2023-06-12 21:32               ` segaloco via TUHS
2023-06-12 21:28             ` Anthony Martin
2023-06-12 20:25         ` Steve Nickolas
2023-06-12 20:17   ` Dave Horsfall
2023-06-12 21:31     ` Clem Cole
2023-06-12 21:39       ` G. Branden Robinson
2023-06-12 22:39         ` Clem Cole
2023-06-12 22:50           ` G. Branden Robinson
2023-06-12 23:04           ` Paul Winalski
2023-06-12 22:09       ` Paul Winalski
2023-06-13  5:28       ` Dave Horsfall
2023-06-13 16:37         ` ron minnich

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=21D1C841C4310FE1829023B424252295.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    --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).