supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Steve Litt <slitt@troubleshooters.com>
To: dng@lists.dyne.org
Cc: supervision@list.skarnet.org
Subject: Be prepared for the fall of systemd
Date: Mon, 01 Aug 2022 03:21:28 -0400	[thread overview]
Message-ID: <4234078aeca178d4b1b5136a9463617d97cef66b.camel@troubleshooters.com> (raw)

Hi all,

As I said in a previous message, I see sentiment very slowly turning against
systemd. If systemd keeps losing popularity, I have no doubt the corporate
carpetbaggers will try to force an even worse atrocity on us, so we need to be ready
this time and not have the argument centered on a false choice.

I see two init systems ready to take the baton and run with it:

* Runit
* S6

Runit is the simplest init system other than /bin/bash or an rc script. It's
maintained by the Void Linux project, so hit hard at the FUDdists who claim runit is
unmaintained.

S6 is advancing full speed to a complete solution, implementing all the best
features of systemd, but these features are voluntary and separable. If you want top
quality, choice and performance, and are willing to accept a little more complexity
(but sane complexity), S6 plus its service manager is the way to go. In my opinion,
S6 plus its service manager offers more than OpenRC, and IMHO it's easier to
configure/manage.

If and when systemd falls, we need to be ready, so we can get the right init system,
instead yet another corporate sponsored Rube Goldberg Machine.

SteveT

             reply	other threads:[~2022-08-01  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  7:21 Steve Litt [this message]
2022-08-03 17:19 ` J.R. Hill
2022-08-04  8:21   ` Steve Litt
2022-08-04  9:09     ` Tanuj Bagaria
2022-08-04 10:33       ` Laurent Bercot
2022-08-05 21:28         ` Daniel Fitzpatrick
2022-08-04 10:59       ` Jan Bramkamp
     [not found]   ` <CAK2MWOvJfx6kB8wiLL4OfgFx25et=_-2OZCsS4VPLYpuBfngyQ@mail.gmail.com>
2022-08-04  8:55     ` [DNG] " Steve Litt
2022-08-04  9:29       ` Laurent Bercot

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=4234078aeca178d4b1b5136a9463617d97cef66b.camel@troubleshooters.com \
    --to=slitt@troubleshooters.com \
    --cc=dng@lists.dyne.org \
    --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).