supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: fungal-net <fungalnet@obarun.org>
To: supervision@list.skarnet.org
Subject: Re: State of skarnet.org projects
Date: Mon, 3 Feb 2020 23:22:12 +0200	[thread overview]
Message-ID: <34b1b27d-2107-8b0b-3ed7-873431a88e55@obarun.org> (raw)
In-Reply-To: <20200203114134.2cab3757@mydesk.domain.cxm>



Steve Litt:
> On Mon, 3 Feb 2020 11:40:07 +0200
> fungal-net <fungalnet@obarun.org> wrote:
> 
>> Steve Litt:
>>> On Sun, 2 Feb 2020 12:34:05 +0200
>>> fungal-net <fungalnet@obarun.org> wrote:
>>>   
>>>> Void is also
>>>> very close, I for one use it with s6 and 66 for a while now and in
>>>> many ways being more carefree than obarun having fast balls thrown
>>>> by arch daily.  
>>>
>>> Have you, or are you going to, write documentation on how to install
>>> and maintain s6 (and presumably s6-rc) on Void? Are you using Void's
>>> s6* packages, or do you compile the stuff yourself? If you install
>>> Void's s6* packages, does that remove runit? I'd like to have both,
>>> to a/b them against each other and to more quickly learn s6*.  
>>
>> All s6 related packages are available on the repository (I believe all
>> current).  I think this work begun and was carried out by Duncaen (a
>> void main member) and he didn't give up, he just realized I think that
>> it would take fundamental void changes to incorporate it as an
>> official alternative.
>> Mobinmob stepped in and brought 66 and libs into void and is
>> maintaining them (currently 1 version behind obarun).  The official
>> documentation for 66 is https://web.obarun.org/software as well as
>> https://wiki.obarun.org/ and due to cross-distribution rules and
>> requests Eric caved into the pressure and provides both html and man
>> pages in the 66 pkg and tools.
>> What is missing from void are the ready made service files that are
>> available to copy/paste from https://framagit.org/pkg/observice
>> and place them into  /usr/share/66/service (instead of obarun's
>> /usr/lib/66/service).  The most important is the boot bundle enabled
>> in the boot tree.
>> https://web.obarun.org/software/66/frontend.html  --> Prototype
>> template of a service file.  Use only the fields that pertain to your
>> service
> 
> If I read between the lines, it sounds like you're saying the
> best way to learn s6 is to install and run Obarun. I have a spare
> machine on which I could do that.

No, I didn't mean to convey such message, it is best to try both s6 and
66 in the distro you are most familiar with.  Here is an example of
trying it on antiX http://sysdfree.wordpress.com/291

As I see mobinmob's response, he is being modest and very reserved.
Void works great with s6/66.  On my experience only ntpd service needed
a small alteration to work out of the box from obarun to void due to the
ntp/openntp difference.  Running resources on the same installation were
nearly identical.  I can't justify and quantify it but it feels the
system became more responsive (quicker).

> Do you think the best and easiest way of learning s6 and the best way
> to use s6 is to install Obarun?

If you can clone your void installation on the same system, different
partition and boot it, do the switch there so you have a better base to
compare with.  If you make the transformation through chroot you will
not have to worry about poweroff/reboot failing, or save runit's reboot
temporarily for that one time.
Pay attention to how void splits some packages into elements so there
may be pkg-n and pkg-n-dev that makes the whole.  This applies to both
s6 and 66.
Feel free to send me any questions on the test.

> Thanks,
> SteveT
> 
> Steve Litt 
> February 2020 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/thrive




  parent reply	other threads:[~2020-02-03 21:22 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 [this message]
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
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=34b1b27d-2107-8b0b-3ed7-873431a88e55@obarun.org \
    --to=fungalnet@obarun.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).