Sample Configuration

Sample Configuration

[ImNotPC]

Hey Group,

I'm building a Linux system based on musl and Busybox. I'm considering 
using s6/s6-rc as an init/supervision system. I see there are good docs 
on all the skanet.org programs, but I can't find an example of a working 
configuration that puts them together. Is there an example available 
somewhere?

Jeff

Re: Sample Configuration

[Carlos Eduardo]

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Check out Artix Linux for a traditional Linux distribution that uses s6
[1]. The s6-scripts link might be the most useful to you, as it's the
"nitty-gritty" (PID 1 initialization and basic daemons).

Laurent is involved in s6-overlay [2], which is geared towards containers
but provides a lot of insight into how to use s6 on a "real" system.

Shameless plug: my own quickstart guide for s6 on Gentoo [3]

[1] https://gitea.artixlinux.org/artix/s6-scripts
https://gitea.artixlinux.org/artix/s6-services
[2] https://github.com/just-containers/s6-overlay
[3] https://wiki.gentoo.org/wiki/User:Capezotte/s6_on_Gentoo

Em sáb., 6 de abr. de 2024 17:44, ImNotPC <imnotpc@rock3d.net> escreveu:

> Hey Group,
>
> I'm building a Linux system based on musl and Busybox. I'm considering
> using s6/s6-rc as an init/supervision system. I see there are good docs
> on all the skanet.org programs, but I can't find an example of a working
> configuration that puts them together. Is there an example available
> somewhere?
>
> Jeff
>
>

Re: Sample Configuration

[prowler_gr.yahoo.gr via supervision]

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.
 
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.

Regards
ProwlerGr


Στις Κυριακή 7 Απριλίου 2024 στις 06:44:58 π.μ. GMT+10, ο χρήστης ImNotPC <imnotpc@rock3d.net> έγραψε: 





Hey Group,

I'm building a Linux system based on musl and Busybox. I'm considering 
using s6/s6-rc as an init/supervision system. I see there are good docs 
on all the skanet.org programs, but I can't find an example of a working 
configuration that puts them together. Is there an example available 
somewhere?

Jeff

Re: Sample Configuration

[prowler_gr.yahoo.gr via supervision]

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

Re: Sample Configuration

[ImNotPC]

On 4/6/24 17:20, Carlos Eduardo wrote:
> Check out Artix Linux for a traditional Linux distribution that uses s6
> [1]. The s6-scripts link might be the most useful to you, as it's the
> "nitty-gritty" (PID 1 initialization and basic daemons).
>
> Laurent is involved in s6-overlay [2], which is geared towards containers
> but provides a lot of insight into how to use s6 on a "real" system.
>
> Shameless plug: my own quickstart guide for s6 on Gentoo [3]
>
> [1] https://gitea.artixlinux.org/artix/s6-scripts
> https://gitea.artixlinux.org/artix/s6-services
> [2] https://github.com/just-containers/s6-overlay
> [3] https://wiki.gentoo.org/wiki/User:Capezotte/s6_on_Gentoo

Thank-you. That gives me plenty of things to look at.

Jeff

Re: Sample Configuration

[ImNotPC]

On 4/6/24 22:40, prowler_gr.yahoo.gr via supervision 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.
>   
> 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.
>
> Regards
> ProwlerGr

Thank-you. I will check these out.

Jeff

Re: Sample Configuration

[Laurent Bercot]

>I'm building a Linux system based on musl and Busybox. I'm considering using s6/s6-rc as an init/supervision system. I see there are good docs on all the skanet.org programs, but I can't find an example of a working configuration that puts them together. Is there an example available somewhere?

  In addition to everything that has been said, you could check out
lh-bootstrap. https://github.com/skarnet/lh-bootstrap

  It's a tool I use to build a complete VM using musl, busybox and 
skarnet.org
utilities from scratch, so I can test it under qemu. The layout of the
filesystem there should give you an idea of how I intend the whole thing
to be used. ;)

--
  Laurent

Re: Sample Configuration

[ImNotPC]

On 4/7/24 07:25, Laurent Bercot wrote:
>> I'm building a Linux system based on musl and Busybox. I'm 
>> considering using s6/s6-rc as an init/supervision system. I see there 
>> are good docs on all the skanet.org programs, but I can't find an 
>> example of a working configuration that puts them together. Is there 
>> an example available somewhere?
>
>  In addition to everything that has been said, you could check out
> lh-bootstrap. https://github.com/skarnet/lh-bootstrap
>
>  It's a tool I use to build a complete VM using musl, busybox and 
> skarnet.org
> utilities from scratch, so I can test it under qemu. The layout of the
> filesystem there should give you an idea of how I intend the whole thing
> to be used. ;)
>
> -- 
>  Laurent
>
Hmmm... it appears lh-bootstrap already does most of what I'm trying to 
achieve. I was probably going to use a simple runit configuration 
because the s6 universe seemed to complex for me to figure out in a 
reasonable amount of time. I haven't dug into it yet so I don't know if 
I can use the tool itself to build my system, but building a working 
example gives me everything I need to see how things go together. 
Thanks, you've all been very helpful!

Jeff

Re: Sample Configuration

[Laurent Bercot]

>was probably going to use a simple runit configuration because the s6 universe seemed to complex for me to figure out in a reasonable amount of time. I haven't

  A basic s6 system is barely more complex than a runit system. This page
should help you start:
  https://skarnet.org/software/s6-linux-init/quickstart.html

  HTH,

--
  Laurent

Re: Sample Configuration

[ImNotPC]

On 4/7/24 15:31, Laurent Bercot wrote:
>> was probably going to use a simple runit configuration because the s6 
>> universe seemed to complex for me to figure out in a reasonable 
>> amount of time. I haven't
>
>  A basic s6 system is barely more complex than a runit system. This page
> should help you start:
>  https://skarnet.org/software/s6-linux-init/quickstart.html 

Ah, I saw the s6-linux-init link but didn't realize what was in it. 
Everything is there on your site but it takes a bit of digging to find 
it. May I humbly suggest adding a 'Starting Out with s6' page to the 
site with some of the info you've all given to me all on one page? It 
would save you from being bothered (as much) by amateurs like me.

Cheers, Jeff

Re: Sample Configuration

[eric via supervision]

On 4/7/24 4:10 PM, prowler_gr.yahoo.gr via supervision wrote:
> 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).
No, it's not a wrapper around s6-rc anymore. 66 is now an independent 
service manager using s6 as process supervisor.
> 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

Re: Sample Configuration

[prowler_gr.yahoo.gr via supervision]

I stand corrected Eric.

The latest version (0.7.0.0) of the 66-suite which you wrote & helped build for antiX, and is what is used on the other Debian based 'init-diversity' spins I posted in this thread, is a complete re-write & now independent of s6-rc (in contrast to the previous version which was a wrapper around s6-rc).

It is a very elegant implementation of s6, & a very popular option even outside Obarun thanks to your personal commitment & contribution on distros that you're no affiliated with such as antiX & Void.









Στις Δευτέρα 8 Απριλίου 2024 στις 11:57:32 π.μ. GMT+10, ο χρήστης eric via supervision <supervision@list.skarnet.org> έγραψε: 






On 4/7/24 4:10 PM, prowler_gr.yahoo.gr via supervision wrote:
> 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).
No, it's not a wrapper around s6-rc anymore. 66 is now an independent 
service manager using s6 as process supervisor.

> 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

Re: Sample Configuration

[prowler_gr.yahoo.gr via supervision]

I can second what Mr Skarnet has stated here.

antiX has a very simple runit implementation & a GUI service-manager which allows the end user to start init scripts & enable them on start-up.

We were able to adapt that GUI service-manager program to work for s6-rc which is able to automate the compilation of service files, adding them to a startup bundle (that is controlled through the GUI), & also binging up services & logs or stopping them.

This has been ported & available on all the 'init-diversity' spins I linked to earlier in this thread.




Στις Δευτέρα 8 Απριλίου 2024 στις 05:31:58 π.μ. GMT+10, ο χρήστης Laurent Bercot <ska-supervision@skarnet.org> έγραψε: 





>was probably going to use a simple runit configuration because the s6 universe seemed to complex for me to figure out in a reasonable amount of time. I haven't

  A basic s6 system is barely more complex than a runit system. This page
should help you start:
  https://skarnet.org/software/s6-linux-init/quickstart.html

  HTH,


--
  Laurent

Re: Sample Configuration

[Laurent Bercot]

>It is a very elegant implementation of s6

  Vocabulary nitpick: no, 66 is not an "implementation of s6".

  s6 is not a specification. It is a software package. So, there is no 
other
"implementation of s6" than the s6 software package itself.

  66 is a service manager than runs on top of the s6 process supervision
suite. It is an implementation of the "service manager" concept. It uses
the s6 interface.

  Just making sure we're using the correct terms. It helps prevent
misunderstandings. :)

--
  Laurent