From: Jonathan Gray <jsg@jsg.id.au>
To: Alexis <flexibeast@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Initial uses of the '-d' convention for daemons?
Date: Sat, 4 Feb 2023 16:02:16 +1100 [thread overview]
Message-ID: <Y93m2I2GGwOYw3bS@largo.jsg.id.au> (raw)
In-Reply-To: <87zg9udpt2.fsf@ada>
On Sat, Feb 04, 2023 at 03:10:26PM +1100, Alexis wrote:
>
> Hi all,
>
> Firstly, thanks to Warren for adding me to the list!
>
> The 6th Edition manual refers to 'cron', not 'crond' (even though cron was
> indeed referred to as a 'daemon'). By 4.2BSD, however, we have things like
> 'telnetd' and 'tftpd'.
>
> Does anyone have any pointers as to when and where the '-d' convention
> started to be used?
The 2nd edition manual has:
dpd(I) spawn data-phone daemon
by the 5th edition, there was also:
lpd(VIII) line printer daemon
The term dates back to CTSS and Multics.
next prev parent reply other threads:[~2023-02-04 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 4:10 [TUHS] " Alexis
2023-02-04 5:02 ` Jonathan Gray [this message]
2023-02-04 5:51 ` [TUHS] " Alexis
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=Y93m2I2GGwOYw3bS@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=flexibeast@gmail.com \
--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).