From: Jeff <sysinit@yandex.com>
To: supervision@list.skarnet.org
Subject: correct init
Date: Thu, 16 May 2019 17:33:46 +0200 [thread overview]
Message-ID: <921971558020826@sas2-c434f6e124b6.qloud-c.yandex.net> (raw)
new postulation:
process #1 should not rely on conditions that it has not previously
ascertained to be true (eg by setting something up by itself, so it
exists and is safe to use/rely on it).
sounds self-evident ? sadly many inits do not comply with that
postulation, a well known example that comes immediatly to mind
is the poorly designed/though out SysV init itself.
the poor crap relies on the initctl fifo for ipc, how dumb can one be ?
next reply other threads:[~2019-05-16 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 15:33 Jeff [this message]
2019-05-16 15:52 ` Jeff
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=921971558020826@sas2-c434f6e124b6.qloud-c.yandex.net \
--to=sysinit@yandex.com \
--cc=supervision@list.skarnet.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).