From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: what init systems do you use ?
Date: Mon, 13 May 2019 23:34:59 -0300 [thread overview]
Message-ID: <CADQ2Nw_LhgOCv4W_eWNwp5=M6y-dq836uV_mv83T-Q5MOLtGxA@mail.gmail.com> (raw)
In-Reply-To: <20190513170948.0a5efc35@mydesk.domain.cxm>
El lun., 13 may. 2019 a las 18:09, Steve Litt escribió:
>
> […] not to sysvinit's
> comments-actually-mean-something five function essay length init
> scripts.
AFAIK, technically those are LSB-style init scripts, and have nothing
to do with sysvinit 'proper' (upstream sysvinit, that I believe Debian
packages as sysvinit-core + sysvinit-utils + bootlogd + ...), which
only understands /etc/inittab. Sysvinit a.k.a. van Smoorenburg init is
just the init program, plus telinit, shutdown, halt, poweroff, reboot,
and some other support programs, and seems to be conflated too often
with the (mostly) shell-based rc subsystem that Debian and derivatives
ship with (sysv-rc + initscripts + lsb-base init-system-helpers +
insserv + …). And which is probably the only one that uses LSB-style
init scripts these days.
G.
next prev parent reply other threads:[~2019-05-14 2:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:19 interesting claims Jeff
2019-04-30 2:49 ` Guillermo
2019-04-30 8:22 ` Laurent Bercot
2019-05-03 0:53 ` what init systems do you use ? Jeff
2019-05-11 18:45 ` Guillermo
2019-05-13 19:13 ` multiplexd
2019-05-13 20:36 ` Laurent Bercot
2019-05-13 21:09 ` Steve Litt
2019-05-14 2:34 ` Guillermo [this message]
2019-05-13 21:16 ` Joshua Ismael Haase Hernández
2019-05-14 5:50 ` Colin Booth
2019-05-14 7:15 ` eric vidal
2019-04-30 8:47 ` interesting claims Jonathan de Boyne Pollard
2019-05-01 7:26 ` Steve Litt
2019-05-01 7:33 ` Steve Litt
2019-05-01 18:13 ` Laurent Bercot
2019-05-15 17:22 ` Steve Litt
2019-05-15 23:22 ` Oliver Schad
2019-05-16 1:07 ` Steve Litt
2019-05-16 5:36 ` fungal-net
2019-05-16 8:32 ` Laurent Bercot
2019-05-16 17:10 ` Jeff
2019-05-17 0:23 ` Dewayne Geraghty
2019-05-17 11:21 ` fungal-net
2019-05-17 22:57 ` Guillermo
2019-05-18 0:52 ` Jeff
2019-05-18 16:26 ` fungal-net
2019-05-18 20:04 ` Guillermo
2019-05-19 11:24 ` fungal-net
2019-05-19 12:57 ` killall test run Jeff
2019-05-19 17:29 ` Colin Booth
2019-05-19 20:39 ` Guillermo
2019-05-19 23:06 ` Laurent Bercot
2019-05-19 20:35 ` interesting claims Guillermo
2019-05-03 1:37 ` how to handle system shutdown ? Jeff
2019-05-03 19:25 ` Laurent Bercot
2019-05-05 0:52 ` is it required to call kill() from process #1 ? 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='CADQ2Nw_LhgOCv4W_eWNwp5=M6y-dq836uV_mv83T-Q5MOLtGxA@mail.gmail.com' \
--to=gdiazhartusch@gmail.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).