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 _at_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_at_disroot.org> έγραψε:
On 7 April 2024 02:40:56 UTC, "prowler_gr.yahoo.gr via supervision" <supervision_at_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
Received on Sun Apr 07 2024 - 07:10:38 CEST