Breaking News: VOID – S6 – Obarun’s 66 – musl

The best of ALL WORLDS has come together!

VOID-linux + s6 + 66 + musl

 

# xbps-query -Rs musl | grep "[*]"
[*] musl-1.1.22_1                             The musl C library
[*] musl-fts-1.2.7_3                          Implementation of fts(3) for musl libc
# xbps-query -Rs s6               
[-] 66-0.1.0.0_1                    Helpers tools around s6-rc
[-] 66-devel-0.1.0.0_1              Helpers tools around s6-rc - develelopment files
[-] 66-doc-0.1.0.0_1                Helpers tools around s6-rc - documentation
[-] s6-2.8.0.0_1                    Small suite of programs for UNIX, designed to allow process supervi...
[-] s6-devel-2.8.0.0_1              s6 supervision library and headers
[-] s6-dns-2.3.0.2_2                Suite of DNS client programs and libraries for Unix systems
[-] s6-dns-devel-2.3.0.2_2          Suite of DNS client programs and libraries for Unix systems - devel...
[-] s6-dns-doc-2.3.0.2_2            Suite of DNS client programs and libraries for Unix systems - docum...
[-] s6-doc-2.8.0.0_1                s6 supervision documentation
[-] s6-linux-utils-2.5.0.1_1        Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e...
[-] s6-linux-utils-doc-2.5.0.1_1    Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e...
[-] s6-networking-2.3.0.4_1         Suite of small network utilities for Unix systems
[-] s6-networking-devel-2.3.0.4_1   Suite of small network utilities for Unix systems - development files
[-] s6-networking-doc-2.3.0.4_1     Suite of small network utilities for Unix systems - documentation
[-] s6-portable-utils-2.2.1.3_2     Tiny portable generic utilities (s6-cat, s6-chmod, etc.)
[-] s6-portable-utils-doc-2.2.1.3_2 Tiny portable generic utilities (s6-cat, s6-chmod, etc.) - document...
[-] s6-rc-0.5.0.0_2                 Service manager of the s6 init system
[-] s6-rc-doc-0.5.0.0_2             Service manager of the s6 init system - documentation

Did you know?  And you didn’t tell me?  Void has been working hard in the background im-porting s6 into the distribution.  Now void ported 66, the newly released Obarun suite of administrative tools for S6, into Void.  Not only that, s6 and 66 are available for both Voids, glibc and musl.

It is like a dream come true.  It is like the future here, now!  It is the best anyone can ask for all in one place.

If there was a war front against systemd and the axis powers, Void and Obarun seem to have crossed deep into enemy lines.  May 9th is not that far!  First we take Warsaw, then we take Berlin.

Ok, tomorrow is another day, of cloning void-musl, removing runit, and then see if we can get s6 and 66 to boot and work just as well as they do in Obarun.  Finally a day to look forward to!

 

5 thoughts on “Breaking News: VOID – S6 – Obarun’s 66 – musl

  1. For now I have given up on musl, I have given up on glibc as well. Maybe at a later stage of development I will try again. One question remains in the back of my head though. In the past I had followed the unorthodox way of removing runit from a void installation and all init related matters, I installed through chroot from arch s6, s6opts, and services as they exist in Obarun, together with an arch kernel. Later I did the same with 66. It worked both times. Installing the same “now native” to void packages and trying all sorts of things it was impossible to boot.

    So s6 and s6-rc in void is not the same as in Obarun, but Obarun’s version works on void. I assume that the 66 transfer is not as hacked. I understand void’s policy of keeping things simple and s6 does not necessarily meet that guideline, runit does.

    For now I have to wait for a later stage of implementation or specific guidelines and documentation from the devs and maintainers about what to do.

    Like

  2. Any update on this?
    Also, I’m not sure about the “working hard in the background on porting s6 into the distro” part. The last time I asked around, it seemed like the devs were very reluctant to exchange runit for s6.
    There was an effort by Duncaen ( https://github.com/Duncaen/void-s6-rc ), but that was before 66 and got abandoned. Maybe it’s worth asking again.

    Like

  3. S6 must be the greatest thing that has hit planet earth since the PC was invented and common mortals can experiment without mind boggling budgets. For many of us it may be years of careful theoretical study before we can comprehend what it does. So we have to be satisfied by the words of those who do know to see it as a great thing.

    Trying to make sense of it all I follow a couple of lists run on skarnet on s6 and service supervision. There are many people there ranging from runit fans and devs, to busybox, to custom sysv and hybrid systems. I admit, much of what they talk about is way over my head 🙂 There is this one guy (Casper Vector maybe) I recently found out who runs void among other things, and he has used s6 with void-glibc before it got to the repositories. I will try to ask him and find out if he has a personal repository where he shares the scripts and his s6-rc.

    I don’t think Duncaen is willing to fiddle with it more, probably no time, nor do I believe void will make the switch. I have no idea whether he ever made s6 and void happy with each other.

    The person that had ported 66 into void repositories is not giving up and the porting is 100% the same with Obarun’s original. But I think the key is to get dracut and s6 to play well with each other. I suspect it will be coming soon. He is busy right now too, so not much is moving right now. Adelie must be getting really close as the creator of S6 is on that team. Damn I am good at picking the right horses to score against systemd 🙂 Remember Adelie is still a beta system, an 0,99999beta but not an 1 yet.

    For the rest of us common mortals the only way to see s6/66 in action is Obarun. Imagine if it was true, out of 500 active distros, the #1 most advanced init system is employed by 1 distro.

    Like

  4. Thank you for the detailed insight. And please keep us updated.
    I hope s6 will become a thing with void eventually.

    On another note, you are also involved in the Obarun community, right?
    What reason does Obarun have to stick to Arch instead of Void in the year 2019?
    They are doing great work, but I’m not going back to Arch after entering the Void.

    Like

  5. Obarun is a challenger, to keep Arch running without systemd was a bet. Void is a distribution that is 100% built from upstream pkgs to run with runit. Runit and s6 are the closest cousins of all init systems. It should not take too long to implement s6 on void. Once s6-rc is configured around Void’s kernel then 66 can take over. Without a front-end like 66 S6 can be a handful to set up.

    I like Void too, but I am also addicted to pacman, while I am still learning it. Xbps may be similar but it is too much syntax to memorize effectively. Just simple tasks (pacman -Syu –> xbps-install -Su or pacman -R –> xbps-remove or pacman -Ss –> xbps-query -Rs) and this is after I had spent years with Debian. Debian’s apt/apt-get is like a chissel compared to a power-drill. When arch will become impossible to deal with without systemd I will most likely end up in void.

    Also Void’s philosophy is not so compatible with S6. Void is aiming for the simplest and lightest solution, one that is manageable by the majority of users. Void is not aiming to replace RHEL in commercial grade enterprise systems, because runit can’t handle it. S6 can!

    Like

If your comment is considered off-topic a new topic will be created with your comment to continue a different discussion. This community is based on open and free communication, meaning we must all respect all in minimizing the exercise of freedom to disrupt such communication. Feel free to post what you think but keep in mind the subject matter discussed. It is just as easy to start a new topic as it is to dilute the content of an existing discussion.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.