From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: s6-rc user experience question
Date: Mon, 17 Oct 2022 21:32:22 +0000 [thread overview]
Message-ID: <emd79d1f80-7f11-4fe1-baca-48889a5429c2@320c5e58.com> (raw)
In-Reply-To: <20221017154328.xcf35bdlabow6bjo@localhost>
> Perhaps a higher-level orchestration tool(s) is/are needed, that
>will accomplish most typical workflows like: (...)
These are all valid points, and things that ultimately s6-frontend,
the future UI over s6/s6-linux-init/s6-rc, aims to solve.
"Higher-level interface" is the (now) #1 feature request for the s6
family of tools, so be assured I've heard it. :)
No promises on the date of delivery, but it's definitely on the radar.
--
Laurent
next prev parent reply other threads:[~2022-10-17 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 6:28 Ihor Antonov
2022-10-16 10:39 ` Laurent Bercot
2022-10-16 16:02 ` Ihor Antonov
2022-10-17 13:11 ` Laurent Bercot
2022-10-17 15:43 ` Ihor Antonov
2022-10-17 21:32 ` Laurent Bercot [this message]
2022-10-18 1:13 ` Alexis
2022-10-18 3:14 ` Ihor Antonov
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=emd79d1f80-7f11-4fe1-baca-48889a5429c2@320c5e58.com \
--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).