supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Dmitry Bogatov <KAction@debian.org>
To: Steve Litt <slitt@troubleshooters.com>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: Is s6/s6-rc ready to be the ubiquitous init?
Date: Sat, 12 Jan 2019 12:41:30 +0000	[thread overview]
Message-ID: <E1giIbU-00040n-Fg@eggs.gnu.org> (raw)
In-Reply-To: <20190111012453.22f63228@mydesk.domain.cxm>


[2019-01-11 01:24] Steve Litt <slitt@troubleshooters.com>
> Hi all,
> 
> Months ago IBM bought Redhat, and IBM might not want to throw a million
> a year at a dev group devoted to keeping the systemd leaky boat afloat.
> Meanwhile, just today another major systemd snafu emerged.
> 
> If IBM bails on systemd, is s6/s6-rc ready to take its place? I mean we
> all know it's ready technically, and is well maintained, but is it ready
> politically, with help for distro packagers? Perhaps some documentation
> on best practices and making it easy to install s6/s6-rc.
> 
> We could soon have a rare opportunity for a Linux-wide init change. I'd
> hate to see systemd replaced by more snake oil.

Wish it was true, and systemd got abandoned.  While I am already
maintaining runit as init system in Debian (and do not spare cycles for
another init system), probably I could provide some assistance --
sponsor uploads, for example.

But currently, s6 is quite out-of-radars in Debian.


      parent reply	other threads:[~2019-01-12 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  6:24 Steve Litt
2019-01-12 11:37 ` Laurent Bercot
2019-02-02  3:13   ` Steve Litt
2019-02-02  9:31     ` Laurent Bercot
2019-01-12 12:41 ` Dmitry Bogatov [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=E1giIbU-00040n-Fg@eggs.gnu.org \
    --to=kaction@debian.org \
    --cc=slitt@troubleshooters.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).