From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: s6-linux-init-1.0.0.0 (was: special s6-svscan/perp(d) catch-all logger service option)
Date: Fri, 26 Apr 2019 09:28:40 +0000 [thread overview]
Message-ID: <em0a21ac15-792a-4307-ba4e-7ead20394014@elzian> (raw)
In-Reply-To: <CADQ2Nw-=rf4uRqbT8ziKoq-bgFqN1K3w0Ny985+J_JemHds96A@mail.gmail.com>
>I saw this a couple of days ago in the Git repository. So, what's your
>stance on the (soon to be) 'old' execline stage1, stage3 and
>.s6-svscan/SIGxxx files approach? Will you consider it deprecated, or
>just an alternative to the s6-linux-init-1.0.0.0 approach? Are the
>version 0.4.0.1 s6-linux-init-maker scripts going to be preserved
>somehow, for inspiration as you say?
Yeah, it's going to be deprecated, because there's a lot of
functionality missing and it's good for playing but not for
integration in distributions, which is my current focus.
But s6-linux-init-0.4.0.1 isn't going anywhere, you will still be
able to download it from the web site or to build it from git,
and I don't expect it to bitrot any soon.
--
Laurent
prev parent reply other threads:[~2019-04-26 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 3:28 Guillermo
2019-04-26 9:28 ` 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=em0a21ac15-792a-4307-ba4e-7ead20394014@elzian \
--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).