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-skaware-csDn2i8iPApAfugRpC6u6w@public.gmane.org>
To: "Steve Litt"
	<slitt-yaXoyPJ8lGSnFU2ba5o1QkEOCMrvLtNR@public.gmane.org>,
	supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org,
	"skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org"
	<skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org>
Subject: Re: State of skarnet.org projects
Date: Sun, 02 Feb 2020 15:58:12 +0000	[thread overview]
Message-ID: <em6db1401f-91b5-42cb-8664-6cb195eb8638@elzian> (raw)
In-Reply-To: <20200202094227.2084ed54-s1DAj2AW31EXSucajVqtjwC/G2K4zDHf@public.gmane.org>

>Do you mean they don't like editing files and creating symlinks? Do
>they want a GUI interface to the service directory tree and the symlink
>tree?

No, it's about service startup with s6-rc. They don't want to dive into
the unpalatable blobs that are the set of systemd unit files or the set
of openrc init scripts (and I can undertand their reluctance); and
they don't want to make the effort of understanding the s6-rc syntax and
creating s6-rc source directories (and that's something I'm sure you can
relate with ;)). They want a service startup configuration format that's
close to what they are used to, typically text files that are easy for
a human to read.

Ideally, they'd want systemd unit files. Which is not gonna happen,
because the format of these files maps the systemd architecture too
closely and there are lots of things that would be expressed differently
under a s6-linux-init/s6/s6-rc system; but a text-based configuration
engine is totally doable, it's just a long project.

They also want high-level commands like "service" or "openrc" to control
the machine state without having to undertand the nitty-gritty of
"s6-rc change", or the difference between "s6-rc -d change foo" and
"s6-svc -d /run/service/foo". Which makes sense: can *you* tell me what
this difference is? :)

All of this will be solved by s6-frontend, but that's not something I
can work on in the evenings.


>What is UX?

  User experience.

--
  Laurent



  parent reply	other threads:[~2020-02-02 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02  9:34 Laurent Bercot
2020-02-02 10:34 ` fungal-net
2020-02-02 14:07   ` Steve Litt
2020-02-03  9:40     ` fungal-net
2020-02-03 16:42       ` Steve Litt
2020-02-03 20:17         ` eric vidal
2020-02-03 21:22         ` fungal-net
2020-02-03 19:28     ` mobinmob
2020-02-02 14:22   ` Laurent Bercot
2020-02-02 14:38     ` Project funding: was " Steve Litt
2020-02-02 15:37       ` Laurent Bercot
2020-02-02 14:42     ` Steve Litt
     [not found]       ` <20200202094227.2084ed54-s1DAj2AW31EXSucajVqtjwC/G2K4zDHf@public.gmane.org>
2020-02-02 15:58         ` Laurent Bercot [this message]
2020-02-02 21:24           ` eric vidal
2020-02-03 10:36     ` fungal-net

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=em6db1401f-91b5-42cb-8664-6cb195eb8638@elzian \
    --to=ska-skaware-csdn2i8ipapafugrpc6u6w@public.gmane.org \
    --cc=skaware-cfaJnhaL+FNC7f45DRzWBg@public.gmane.org \
    --cc=slitt-yaXoyPJ8lGSnFU2ba5o1QkEOCMrvLtNR@public.gmane.org \
    --cc=supervision-cfaJnhaL+FNC7f45DRzWBg@public.gmane.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).