From: Lars Brinkhoff <lars@nocrew.org>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: coff@tuhs.org
Subject: [COFF] Re: Terminology query - 'system process'?
Date: Fri, 15 Dec 2023 06:24:33 +0000 [thread overview]
Message-ID: <7wv8903rvi.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20231214214805.81B2618C08F@mercury.lcs.mit.edu> (Noel Chiappa's message of "Thu, 14 Dec 2023 16:48:05 -0500 (EST)")
For the record, daring to stray outside Unix, ITS originally had a
"system job", and later split off a "core job". Both running in monitor
mode. Job means the same thing as process here, and monitor same as
kernel.
--- >8 --- cut and stop reading here --- >8 --- off topic --- >8 ---
In ITS terminology, "demon" means a (user space) process that is started
on demand by the system. This could be due to an external event (say, a
network connection), or another process indicating a need for a service.
The demon may go away right after it has done its job, or linger around
for a while.
There's a separate term "dragon" which means a continuously running
background process.
next prev parent reply other threads:[~2023-12-15 6:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 21:48 [COFF] " Noel Chiappa
2023-12-14 22:06 ` [COFF] " Bakul Shah
2023-12-14 22:12 ` Warner Losh
2023-12-14 22:09 ` Clem Cole
2023-12-15 14:20 ` Dan Cross
2023-12-15 16:25 ` Warner Losh
2023-12-15 17:13 ` Bakul Shah
2023-12-15 6:24 ` Lars Brinkhoff [this message]
2023-12-15 18:30 ` Stuff Received
2023-12-14 23:29 Noel Chiappa
2023-12-14 23:54 ` Larry McVoy
2023-12-15 1:15 ` Bakul Shah
2023-12-15 17:51 ` Paul Winalski
2023-12-15 18:08 ` Warner Losh
2023-12-16 2:04 ` Greg 'groggy' Lehey
2023-12-16 19:21 ` Paul Winalski
2023-12-16 19:44 ` Paul Winalski
2023-12-15 13:43 ` Dan Cross
2023-12-19 13:54 ` Derek Fawcus via COFF
2023-12-20 19:31 Noel Chiappa
2023-12-20 20:29 ` Paul Winalski
2023-12-31 3:51 ` steve jenkin
2023-12-20 20:35 Noel Chiappa
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=7wv8903rvi.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=coff@tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
/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).