supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Is s6/s6-rc ready to be the ubiquitous init?
Date: Sat, 02 Feb 2019 09:31:29 +0000	[thread overview]
Message-ID: <em3bc4e836-15fe-4e75-b80e-72c34b3b5e55@elzian> (raw)
In-Reply-To: <20190201221348.2bd5107e@mydesk.domain.cxm>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

>1) Where can I find the s6/s6-rc project's preferred directories for
>    everything?

If there is *one thing* you should know about s6, and that you should
convey to your readers, it is that *it does not provide, or care about,
policy*. I thought it would be abundantly clear by now.

That means there are *no* preferred directories. People can do
whatever they want. Yeah, this is a hard concept to grasp in the era
of systemd, but the Overton window needs a big fat shift towards
flexibility and user choice.

Of course, there are smarter choices than others. I have expressed
and explained my own preferences several times, both in parts of the
s6 and s6-rc documentation, and on this mailing-list when the subject
came up. You can find them in the archives. But these are my
preferences and recommendations, not official policies. Official
policies should be done in the context of a _distribution_.


>  I'd prefer not to put anything directly off the root
>    directory: Too many people would object.

Boy, if your audience is going to clutch their pearls at the mention
of adding something to the root directory, just wait until they hear
about how to write init scripts. :P

Again, directories can be put *wherever*, and you don't have to
create anything in the root directory. But approaching this with
the angle of "I won't say anything radical to avoid scaring my
audience" is the wrong mindset. You will never convince people
who are far enough gone to believe that nothing should ever be
created in the root directory despite having accepted /media without
questioning because it came from a Standard™.


>2) Does there exist a block diagram of either s6,  s6-rc, or both
>    combined, and if so, where?

  Well, dear, that's one of the things that are missing and that
you're going to provide, isn't it?

--
  Laurent

  reply	other threads:[~2019-02-02  9:31 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
2019-02-02  9:31     ` Laurent Bercot [this message]
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=em3bc4e836-15fe-4e75-b80e-72c34b3b5e55@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).