From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15927 invoked from network); 13 Jun 2023 01:49:24 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 13 Jun 2023 01:49:24 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id F012C424FC; Tue, 13 Jun 2023 11:49:20 +1000 (AEST) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) by minnie.tuhs.org (Postfix) with ESMTPS id F0931424F0 for ; Tue, 13 Jun 2023 11:49:11 +1000 (AEST) Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2b1b8593263so60025181fa.2 for ; Mon, 12 Jun 2023 18:49:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686620950; x=1689212950; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Bb9OI+aWt+vec99WBD/PVH5ofAYcLa9Z85KVIhUs0Hs=; b=bL9/7Ru5FYE+HQTgcCQAGCxevwPXusKRa7aoEjbgTzKXVFY85uPaJxeL2HXKWs7p9A /pzQ7G5Lm65O9q0Sl99jtS6xydBu+3lhnTTYH3NMR6/6hkg5WVnThc9vfQtgvisnEPo1 jN4Lnw1dQHJMZ9ecHrzMmcws/APDAK65FcbgVW08gBjzFZ1fndY2oQAMyBMAhqq/W7EH dm0QM/7msnn6fZGPXO292cTYSvBakyHNkF0KFcv4eDJqdePcy48Pr6vHq+Y2xE5P5F7l 5IekMPfGdBXT/PlEaG7ZIZo8Qx9aQrKw5cPlxyfMZTxtJ1juckYathbP+HR9hyJpwobw N3/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686620950; x=1689212950; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Bb9OI+aWt+vec99WBD/PVH5ofAYcLa9Z85KVIhUs0Hs=; b=fCjt1NUDxb9ZExV3axhiE+2icYKbuUa4RiEXthVp03B4iY04pRHeTkun6Vu6wEskjJ A6U4cTSPUH4FUM8jQBmEQilbwQVwaQ6jFY80G1fq5p8N0SmzRcpp2qZiKa5NW9K9Vxlv O6pHU3Oz9sLbxs3HQ69zDs6CjNiEjr8hxR/YY3wZz3sxhYhbmD9eXPAltyPxikedCI0d 5FoJ9CkGc8pirfzLjDfiu2+4AiROEXwe/rQgLZfIdbuu1JHMa/Fovd+nsd8SSyAeCBCs FuuSlncXxy1hPEkrFfBtg5oPaVdCK54e4RDCWWcQFZK45WapOOBLR7g0FANAPPd1FO67 SGnQ== X-Gm-Message-State: AC+VfDwFEcibvjSEYr0XaZCycq0hGpgOaCC0Bhp4gJcl3qUN70dSPZtx jFCfodhuk+jJCxtEB9pkqWsYk8KQcQ3omVSi4NvHYk46 X-Google-Smtp-Source: ACHHUZ5V57kx2AiomJBoh6mTjbFcOn4IEWwtD4VRT/G6rbZwzgFh+RfH3S7WNJQWCBGbCdWF1fu2XgzfZ7jCso++9hU= X-Received: by 2002:a2e:9b1a:0:b0:2b2:1d7a:bd46 with SMTP id u26-20020a2e9b1a000000b002b21d7abd46mr4542435lji.43.1686620949575; Mon, 12 Jun 2023 18:49:09 -0700 (PDT) MIME-Version: 1.0 References: <21D1C841C4310FE1829023B424252295.for-standards-violators@oclsc.org> In-Reply-To: <21D1C841C4310FE1829023B424252295.for-standards-violators@oclsc.org> From: Dan Cross Date: Mon, 12 Jun 2023 21:48:58 -0400 Message-ID: To: Norman Wilson Content-Type: multipart/alternative; boundary="00000000000091fae505fdf90ada" Message-ID-Hash: DDCFME2TSTLQAG43EJ5GBHDBZ7JLQUK7 X-Message-ID-Hash: DDCFME2TSTLQAG43EJ5GBHDBZ7JLQUK7 X-MailFrom: crossd@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: TUHS X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: crt0 -- what's in that name? List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --00000000000091fae505fdf90ada Content-Type: text/plain; charset="UTF-8" On Mon, Jun 12, 2023, 9:37 PM Norman Wilson wrote: > 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? > Not a citation, either, but I believe the original RUNCOM came from CTSS ( https://multicians.org/shell.html), and MDN-4 on the design of the Multics shell mentions the term and MDN-5 goes into detail here. Newer Multics calls this "exec_com", as in the shell startup file ` start_up.ec` that Multics users have in their login directories. https://web.mit.edu/multics-history/source/Multics/doc/info_segments/exec_com.info - Dan C. --00000000000091fae505fdf90ada Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jun 12, 2023, 9:37 PM Norman Wilson <norman@oclsc.org> wrote:
Clem Cole:

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

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

=C2=A0 Soon after TMG became available, Thompson decided that we could not<= br> =C2=A0 pretend to offer a real computing service without Fortran, so he sat=
=C2=A0 down to write a Fortran in TMG.=C2=A0 As I recall, the intent to han= dle
=C2=A0 Fortran lasted about a week.=C2=A0 What he produced instead was a de= finition
=C2=A0 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'.=C2=A0 Not the shell, but the usage as part of a file name.=C2=A0 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).=C2=A0 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.=C2=A0 Anyone
else remember where to look?
=
Not a citation, either, but I believe the origi= nal RUNCOM came from CTSS (ht= tps://multicians.org/shell.html), and MDN-4 on the design of the Multic= s shell mentions the term and MDN-5 goes into detail here.

Newer Multics calls this "exec_com&= quot;, as in the shell startup file `start_u= p.ec` that Multics users have in their login directories. https://web.mit.edu/multics-history/source/Multics/doc/info_segments= /exec_com.info

=C2= =A0 =C2=A0 =C2=A0 =C2=A0 - Dan C.

--00000000000091fae505fdf90ada--