supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: s6-linux-init-1.0.0.0 (was: special s6-svscan/perp(d) catch-all logger service option)
Date: Fri, 26 Apr 2019 00:28:42 -0300	[thread overview]
Message-ID: <CADQ2Nw-=rf4uRqbT8ziKoq-bgFqN1K3w0Ny985+J_JemHds96A@mail.gmail.com> (raw)

Hi,

El jue., 25 abr. 2019 a las 20:10, Laurent Bercot escribió:
>
> I would recommend you to grab the 0.4.0.1 release of s6-linux-init
> and use the stage 1 scripts created by s6-linux-init-maker, either as
> is, or as a source of inspiration for your own stage 1 scripts.
> [...]
> I would also recommend you, or anyone interested in stage 1 script
> creation, to do this sooner rather than later, because a new version
> of s6-linux-init is going to be released in less than a week, and [...]
> stage 1 will be a C program rather than an
> execline script,

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?

Thanks,
G.


             reply	other threads:[~2019-04-26  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  3:28 Guillermo [this message]
2019-04-26  9:28 ` Laurent Bercot

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='CADQ2Nw-=rf4uRqbT8ziKoq-bgFqN1K3w0Ny985+J_JemHds96A@mail.gmail.com' \
    --to=gdiazhartusch@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).