From: Steve Litt <slitt@troubleshooters.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Is s6/s6-rc ready to be the ubiquitous init?
Date: Fri, 1 Feb 2019 22:13:48 -0500 [thread overview]
Message-ID: <20190201221348.2bd5107e@mydesk.domain.cxm> (raw)
In-Reply-To: <em69df4b7f-4017-4c1c-9b37-8e311d06dd49@elzian>
On Sat, 12 Jan 2019 11:37:55 +0000
"Laurent Bercot" <ska-supervision@skarnet.org> wrote:
> >If IBM bails on systemd, is s6/s6-rc ready to take its place? I mean
> >we all know it's ready technically, and is well maintained, but is
> >it ready politically, with help for distro packagers? Perhaps some
> >documentation on best practices and making it easy to install
> >s6/s6-rc.
>
> I'm very thankful for your generous offer to provide documentation
> and tutorials. Help for distro packagers is indeed something s6/s6-rc
> needs. Can you give me an outline of your tutorial when it's ready?
> I'll be happy to proofread it and make suggestions.
You're welcome. The docs and tutorials will roll out slowly, but
they're roll out.
A couple questions:
1) Where can I find the s6/s6-rc project's preferred directories for
everything? I'd prefer not to put anything directly off the root
directory: Too many people would object.
2) Does there exist a block diagram of either s6, s6-rc, or both
combined, and if so, where?
Thanks,
SteveT
Steve Litt
January 2019 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust
next prev parent reply other threads:[~2019-02-02 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 6:24 Steve Litt
2019-01-12 11:37 ` Laurent Bercot
2019-02-02 3:13 ` Steve Litt [this message]
2019-02-02 9:31 ` Laurent Bercot
2019-01-12 12:41 ` Dmitry Bogatov
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=20190201221348.2bd5107e@mydesk.domain.cxm \
--to=slitt@troubleshooters.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).