From: "Alex Efros via supervision" <supervision@list.skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: Answers to some GitHub questions
Date: Wed, 6 Jan 2021 16:56:29 +0200 [thread overview]
Message-ID: <X/XPnRCOnMTxAprX@home.lan> (raw)
In-Reply-To: <eme7ca9413-36f8-4300-acab-fba842d53d26@elzian>
Hi!
Thanks, this was useful reading.
Is there a migration guide from runit to s6?
If not, it might be useful to create one with hints how to rewrite
/etc/runit/{1,3} and runit services in s6-way, what to run instead of
/sbin/runit-init as kernel's init= param, and what to use instead of
`runit-init {0,6}` to halt/reboot. Because, you know, while everything
you've said about runit vs s6 is true, runit is still "just works"… so
without easy-to-follow guide it's hard to find a motivation to move to s6.
--
WBR, Alex.
next prev parent reply other threads:[~2021-01-06 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 0:57 Laurent Bercot
2021-01-06 14:56 ` Alex Efros via supervision [this message]
2021-01-06 18:47 ` Colin Booth
2021-01-09 17:25 ` 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=X/XPnRCOnMTxAprX@home.lan \
--to=supervision@list.skarnet.org \
--cc=powerman@powerman.name \
/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).