supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: [DNG] Be prepared for the fall of systemd
Date: Thu, 04 Aug 2022 09:29:14 +0000	[thread overview]
Message-ID: <emc68be910-80f2-4cb1-a83e-1a16156c9ab9@126e3e73.com> (raw)
In-Reply-To: <df753e2ad420c739563af1ea8467eed407a207ff.camel@troubleshooters.com>


>I find it symptomatic of the fact that a guy wrote some Rube Goldberg code and a
>corporation decided it would be a great idea to spend millions getting the Rube
>Goldberg code into many major distros. As far as us running our of road with the
>Unix API, systemd solves no problem and offers no improvement that couldn't have
>been solved or improved in a dozen different ways, almost all of which would have
>been more modular and less prone to vendor lock in.

  We know all of this.
  Please keep these posts out of the supervision ML. It's not that we
don't like systemd-bashing, it's that it takes a lot of space and makes
a lot of noise, and I'd like the supervision ML to be laser-focused on
solving technical issues with supervision systems, not be yet another
place where we complain about systemd day in day out. Thanks.

--
  Laurent


      reply	other threads:[~2022-08-04  9:29 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
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 [this message]

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=emc68be910-80f2-4cb1-a83e-1a16156c9ab9@126e3e73.com \
    --to=ska-supervision@skarnet.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).