From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] Again about etymology: rc
Date: Wed, 23 Mar 2016 15:30:24 -0400 [thread overview]
Message-ID: <CAEoi9W7v-sYCOyxpw55Zx9x4qZQckfJNntyn9nJYJ6E++DjQtw@mail.gmail.com> (raw)
In-Reply-To: <trinity-e0dd3f63-baa1-4c8c-9a96-128bdb17f897-1458760805118@3capp-mailcom-lxa01>
They stand for, "run-com" as in "run commands": This was the name for a
scripting facility in, I believe, CTSS.
On Wed, Mar 23, 2016 at 3:20 PM, Rocky Hotas <rockyhotas at post.com> wrote:
> Hello everyone,
> I am Rocky and this is my first message. Before starting, I would like to
> thank you for all the valuable informations and stories you post here.
> About the History of Unix, I was wondering with another guy why the rc
> script has that name. As many of you already know, and according to NetBSD,
> FreeBSD, OpenBSD (current) manual,
>
> "The rc utility is the command script which controls" the startup of
> various services, "and is invoked by init(8)" (from DESCRIPTION).
> "The rc command appeared in 4.0BSD" (from HISTORY).
>
> Words may slightly change between the three distributions, but the meaning
> and the informations provided are the same. So, the etymology of rc does
> not appear in the man pages. Do you know how to recover it? Do (or did) the
> letters rc have some meaning in this context?
> Cheers,
>
> Rocky
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160323/4fd384e2/attachment.html>
next prev parent reply other threads:[~2016-03-23 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 19:20 Rocky Hotas
2016-03-23 19:30 ` Dan Cross [this message]
2016-03-23 19:38 ` Diomidis Spinellis
2016-03-23 19:53 ` Mantas Mikulėnas
2016-03-23 19:57 ` Steve Nickolas
2016-03-23 21:14 ` Jeremy C. Reed
2016-03-24 9:59 ` Rocky Hotas
2016-03-24 6:59 ` Dave Horsfall
2016-03-25 1:19 ` Greg 'groggy' Lehey
2016-03-23 22:06 Noel Chiappa
2016-03-24 0:09 ` Clem Cole
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=CAEoi9W7v-sYCOyxpw55Zx9x4qZQckfJNntyn9nJYJ6E++DjQtw@mail.gmail.com \
--to=crossd@gmail.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).