From: "prowler_gr.yahoo.gr via supervision" <supervision@list.skarnet.org>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Sample Configuration
Date: Sun, 7 Apr 2024 05:10:38 +0000 (UTC) [thread overview]
Message-ID: <1365825629.8830378.1712466638671@mail.yahoo.com> (raw)
In-Reply-To: <073399B2-88AD-4997-823F-018700550F96@disroot.org>
66 is a wrapper around s6-rc which brings some very good enhancements, eg declarative service frontend files (similar to systemd unit files), & neater organisation of service bundles/runlevels (called trees).
A good read in regards to 66 service frontend (unit) files can be found here (attention to section “A word about the @execute key”)
https://web.obarun.org/software/66/latest/66-frontend.html
With the current state of s6-rc I would say using the 66 suite wrapper would be my personal most preferred implementation of s6.
Στις Κυριακή 7 Απριλίου 2024 στις 02:48:40 μ.μ. GMT+10, ο χρήστης Adam Faiz <adam.faiz@disroot.org> έγραψε:
On 7 April 2024 02:40:56 UTC, "prowler_gr.yahoo.gr via supervision" <supervision@list.skarnet.org> wrote:
>For anybody interested on s6-rc/s6-66 on Debian based distro's I have created some unofficial spins with multiple inits which work independently from each other.
Thank you! I have my own configuration for both runit and the GNU Shepherd, but I like the elegance of s6-rc and wanted to try it.
>
>The concept is very simple, any init can be installed under a /usr/lib folder, their service files in relevant sub-folders under /etc, & finally grub is configured to recognise any available init under the /lib folders
>
>https://archive.org/details/antix-23.1_init-diversity-edition_UNOFFICIAL_20240302
>https://archive.org/details/Devuan-5.0_xfce_init-diversity-edition_amd64_UNOFFICIAL_20240319
>https://archive.org/details/mx-23.2-kde-init-diversity-edition-unofficial-20240222
>
>
>Technically if you try any of these respins you will find each init works independently from each other (does not try & hijack folders & files used by other inits).
>
>This should provide a good configuration example you might be after for either s6-rc or s6-66.
Do you think 66 is simpler than s6-rc?
>
>Regards
>ProwlerGr
next prev parent reply other threads:[~2024-04-07 5:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 20:44 ImNotPC
2024-04-06 21:20 ` Carlos Eduardo
2024-04-07 10:41 ` ImNotPC
2024-04-07 2:40 ` prowler_gr.yahoo.gr via supervision
[not found] ` <073399B2-88AD-4997-823F-018700550F96@disroot.org>
2024-04-07 5:10 ` prowler_gr.yahoo.gr via supervision [this message]
2024-04-08 1:57 ` eric via supervision
2024-04-08 2:52 ` prowler_gr.yahoo.gr via supervision
2024-04-08 3:17 ` Laurent Bercot
2024-04-07 10:43 ` ImNotPC
2024-04-07 11:25 ` Laurent Bercot
2024-04-07 12:22 ` ImNotPC
2024-04-07 19:31 ` Laurent Bercot
2024-04-07 21:25 ` ImNotPC
2024-04-08 3:04 ` prowler_gr.yahoo.gr via supervision
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=1365825629.8830378.1712466638671@mail.yahoo.com \
--to=supervision@list.skarnet.org \
--cc=adam.faiz@disroot.org \
--cc=prowler_gr@yahoo.gr \
/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).