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@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Can s6 be enough?: was s6-ps
Date: Sun, 06 Jan 2019 07:40:24 +0000	[thread overview]
Message-ID: <em6e592532-7941-4598-a54c-26f3ad53ec0e@elzian> (raw)
In-Reply-To: <20190106053901.GA16647@latitude.localdomain>

>Eliminate dependency on udevd from oneshot startup scripts.

  One example among others:
Kernel events are used to automatically load dynamic kernel modules.
Say you need to mount a filesystem of a type that's not known in your
core kernel, but you have a module for that. Either you manually
modprobe everything in your initial oneshots (which is possible, but
less flexible and more painful), or you just spawn udevd first and
can then mount everything you need.
The latter is clearly the intended use case - that's what automatic
module loading is for. But you can only do that by making oneshots
depend on the udevd longrun.

Don't organize your system around the tools you have. You shouldn't
have to jump through hoops to accommodate mediocre tools/architecture
or distributor laziness; it's a losing game in the end, and the user
is the one who loses.
Instead, get the tools you need so your system works as painlessly
as possible for the user. In some cases, you won't need a service
manager; in most cases, you will.

--
Laurent



  parent reply	other threads:[~2019-01-06  7:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05  0:20 ` s6-ps Laurent Bercot
2019-01-05  4:04   ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46   ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41     ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29     ` s6-ps multiplexd
2019-01-05 20:30     ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22       ` Laurent Bercot
     [not found]         ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06  7:40           ` Laurent Bercot [this message]
2019-01-06 15:03       ` Brett Neumeier
2019-01-07 21:45         ` Steve Litt
2019-01-08  9:19           ` Laurent Bercot
2019-01-05 21:00     ` s6-ps Guillermo
2019-01-06  1:15       ` s6-ps Steve Litt
2019-01-06  7:06       ` s6-ps Colin Booth
2019-01-06  7:30         ` s6-ps Laurent Bercot
2019-01-06 18:07           ` s6-ps Colin Booth

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=em6e592532-7941-4598-a54c-26f3ad53ec0e@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).