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: "Steve Litt" <slitt@troubleshooters.com>,
	Supervision <supervision@list.skarnet.org>
Subject: Re: Is s6/s6-rc ready to be the ubiquitous init?
Date: Sat, 12 Jan 2019 11:37:55 +0000	[thread overview]
Message-ID: <em69df4b7f-4017-4c1c-9b37-8e311d06dd49@elzian> (raw)
In-Reply-To: <20190111012453.22f63228@mydesk.domain.cxm>

>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.

I think you're deluded if you think systemd's going away by a
top-down decision. Corporate likes organizational stability, and
has a lot of inertia. They will keep what they have, they will
keep funding the systemd team, who are, after all, the experts on
systemd, and who will fix the issues (nevermind the fact that
they're also the ones creating them). They are not going to take
a major risk by throwing away their product and using something
they don't know.

Now, *if* someone with important lobbying power could demonstrate
to IBM/RedHat executives that they could do the same thing for
much less effort and much less PR trouble by supporting another
product with a much cheaper team, *then* they might be interested.
But we're not there yet, unless you have high-placed connections I
don't know about. :P


>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.

I'm very thankful for your generous offer to provide documentation
and tutorials. Help for distro packagers is indeed something s6/s6-rc
needs. Can you give me an outline of your tutorial when it's ready?
I'll be happy to proofread it and make suggestions.


>We could soon have a rare opportunity for a Linux-wide init change. I'd
>hate to see systemd replaced by more snake oil.

  So would I. So would, I like to think, most people here. But
systemd isn't going to disappear on a corporate whim. It will have
to be dislodged with pitchforks and torches, and most importantly,
constant lowburn effort by enthusiasts spreading the word.

  The plan is coming along - slowly, *very* slowly because I have to
fund myself, but surely. Next year I'll be working on an interface
for the whole s6 stack that makes it easy for distributions and
administrators to replace systemd with something close to what they
know. Stay tuned.

--
  Laurent



  reply	other threads:[~2019-01-12 11:37 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 [this message]
2019-02-02  3:13   ` Steve Litt
2019-02-02  9:31     ` Laurent Bercot
2019-01-12 12:41 ` Dmitry Bogatov

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=em69df4b7f-4017-4c1c-9b37-8e311d06dd49@elzian \
    --to=ska-supervision@skarnet.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).