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, supervision@list.skarnet.org
Subject: Re: Be prepared for the fall of systemd
Date: Thu, 04 Aug 2022 04:21:36 -0400	[thread overview]
Message-ID: <7ee45cee99f3f84093ca674ac5caaf1e6a8b8421.camel@troubleshooters.com> (raw)
In-Reply-To: <75OjPiNdg7k-TrGOB10JwBnln7qJjJRtcsOdg1Dm_gk72TwWJ2Te1njPOEgXz-khoRDvkvqjOfB2kUNj5_iAXtoHivgeGVZwoUzvQod4vIo=@so.dang.cool>

On Wed, 2022-08-03 at 17:19 +0000, J.R. Hill wrote:
> There are a few things that need to be in place for a smooth transition.
> 
> For general trust in the project...
> 
> 1. the init system itself should be maintained by more than a single human.

This hasn't been the case with runit. It's so darn simple people *do* trust it, even
though it was written by one guy and he stepped away.

> 2. the maintainers should be willing to respond to a large audience. (If a project
> is used widely across distributions and is critical to operation and security,
> it'll attract attention from armies of newbies and large cloud corporations
> alike.) This means there needs to be an ability to move slow (maintain backwards
> compatibility) and also to move fast (in security situations)

True. All I can say is runit does one thing and does it well, appears to have no
known security flaws, has a small attack surface, so there's little call for
updates.

> 3. the project should be available from some trusted platform with versioning and
> source history.
> 
> For ease of transition...
> 
> 4. many init scripts need to exist, or they need to be trivial to write.

The originator of runit gives many example scripts, AND they are trivial to write.
See http://smarden.org/runit/runscripts.html .


> 
> I'll give some thoughts on runit:
> 
> I'll start by saying that I've used Void linux for a few years now, and I love
> using runit. It's simple, it works, and it's understandable. That's the opposite
> of my experience with systemd. I'm not passionately against systemd (or the
> developers, or RedHat, or even IBM), and I think systemd is technically impressive
> and ambitious. But also I don't really want to use it or anything like it.
> 
> > It's maintained by the Void Linux project...
> 
> Unfortunately I don't think this is true. It's used by Void, but we're packaging
> it by building from the source tarball like anyone else.

I guess what I meant was https://github.com/void-linux/runit . That's the source
code, maintained by the Void Linux project, and it's up to individual distros to
package it for their distro.

SteveT

  reply	other threads:[~2022-08-04  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  7:21 Steve Litt
2022-08-03 17:19 ` J.R. Hill
2022-08-04  8:21   ` Steve Litt [this message]
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=7ee45cee99f3f84093ca674ac5caaf1e6a8b8421.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).