From: Alex Suykov <alex.suykov@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: [Announce] s6.rc: a distribution-friendly init/rc framework
Date: Fri, 23 Mar 2018 15:05:53 +0200 [thread overview]
Message-ID: <20180323130553.GA15552@latitude.localdomain> (raw)
In-Reply-To: <emf6ba9bba-7e14-43f1-90a6-3923ac5d6d7d@elzian>
Fri, Mar 23, 2018 at 10:51:57AM +0000, Laurent Bercot wrote:
> Bear in mind that - this is a simplified, but descriptive enough view
> of the political landscape of the current Linux ecosystem - distribution
> maintainers are *lazy*. They already know systemd, or openrc, or
> sysvinit; they don't want to put in more effort. They don't want to have
> to significantly modify their packaging scripts to accommodate a wildly
> different format.
In their defence, I don't think any mainstream distribution makes this
kind of modifications easy. IMO it's safe to assume a new init system
means a new distribution (possibly derived from something larger).
> For instance, instead of having to provide s6-rc source definition
> directories for services, they would provide a descriptive file,
> similar to systemd unit files, that would then be automatically
> processed and turned into a set of s6-rc definition directories.
Extra layers generally make things harder to work with, not easier.
Whoever may be building something new with s6 would probably benefit
more from a reference system that's simple enough to understand
and which could be used as a base for extending into a full blown
distribution. Having examples at hand would likely matter much more
than the format of service description.
The reaction to the slew manual I'm afraid will likely be along the
lines of "that's all cool and stuff but how do I actually run this?".
next prev parent reply other threads:[~2018-03-23 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180322132334.GA11596@caspervector>
2018-03-22 17:10 ` Laurent Bercot
2018-03-23 4:00 ` Casper Ti. Vector
2018-03-23 10:09 ` slew: renamed from "s6.rc" Casper Ti. Vector
[not found] ` <20180323040022.GA1737@caspervector>
2018-03-23 10:51 ` [Announce] s6.rc: a distribution-friendly init/rc framework Laurent Bercot
2018-03-23 13:05 ` Alex Suykov [this message]
2018-03-23 13:31 ` Casper Ti. Vector
2018-03-23 14:19 ` Laurent Bercot
2018-03-23 13:20 ` Casper Ti. Vector
2018-03-25 4:57 ` Casper Ti. Vector
[not found] ` <20180323132058.GA21692@caspervector>
[not found] ` <20180325045750.GA5868@caspervector>
2018-03-25 6:38 ` Laurent Bercot
2018-03-25 9:31 ` Casper Ti. Vector
2019-06-03 9:30 ` Casper Ti. Vector
[not found] ` <20190603093041.GA10891@caspervector>
2019-06-03 16:06 ` Laurent Bercot
2018-03-22 13:23 Casper Ti. Vector
2018-03-22 15:29 ` Casper Ti. Vector
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=20180323130553.GA15552@latitude.localdomain \
--to=alex.suykov@gmail.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).