For those that don’t know about Void and kernels, Void offers many of them at any single period and updates them within 24hr of a new edition. The kernel pkg name for each edition stays the same, but the versions have an extended naming that is also used in making the bootable images. For example, let’s say you are following “linux4.19” and it is currently linux4.19.39-1. Then there might be 4.19.40-1, 4.19.40-2 and so on. If you use vkpurge to list the editions it will show you all except for the current. Let’s say you also follow linux4.14, linux4.20, and linux5.0. You may end up having to remove many kernel editions within a week. Continue reading
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-184.108.40.206_1 Small suite of programs for UNIX, designed to allow process supervi... [-] s6-devel-220.127.116.11_1 s6 supervision library and headers [-] s6-dns-18.104.22.168_2 Suite of DNS client programs and libraries for Unix systems [-] s6-dns-devel-22.214.171.124_2 Suite of DNS client programs and libraries for Unix systems - devel... [-] s6-dns-doc-126.96.36.199_2 Suite of DNS client programs and libraries for Unix systems - docum... [-] s6-doc-188.8.131.52_1 s6 supervision documentation [-] s6-linux-utils-184.108.40.206_1 Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e... [-] s6-linux-utils-doc-220.127.116.11_1 Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e... [-] s6-networking-18.104.22.168_1 Suite of small network utilities for Unix systems [-] s6-networking-devel-22.214.171.124_1 Suite of small network utilities for Unix systems - development files [-] s6-networking-doc-126.96.36.199_1 Suite of small network utilities for Unix systems - documentation [-] s6-portable-utils-188.8.131.52_2 Tiny portable generic utilities (s6-cat, s6-chmod, etc.) [-] s6-portable-utils-doc-184.108.40.206_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
S6 appears as the init system that few distributions have chosen as their default init and service management/supervision (obarun and possibly Adélie once stable is released). There are quite a few commercial servers running on this system. For general personal use s6 seems complex, but complex is not always a bad thing. It would be unfair to compare it with older systems such as SysV-init. Sysvinit is the system that the overwhelming majority of enterprise system administrators had learned on and relied on for decades (yes it is more than one). Upstart seems extinct by now, and OpenRC is getting old as well, and didn’t necessarily deviate much from the path of sysvinit. But then there is Runit. Void and Artix appear the first two we think right away that use it. S6 is a step further into the future of unix-like systems. Continue reading
Just be patient
updated November 8th, see note below
The forum for Void-Linux has been disconnected for about a week and void has not posted anything on their news page. They do have an irc channel at freenode for those who are eager to get in touch about an issue they are having. A month or two ago, the user who had donated the server and was running the forum, not a member of the developers’ team as I understood, had been doing this for a long time and was paying out of his pocket for it and wanted to pass the torch. Without the ability for void to receive or contribute any donations for this purpose the issue was lagging. Void has never been up to this point a formal legal entity. Continue reading
This is short as there is shortage of information on what this means. In detail, but not exactly, read their news
In summary the founder of void, the one that held the keys to all resources, has just vanished (the rest say) without notice, no communication. Luckily there are many people involved in void and seem for the past 4 months to be handling things as usual. Github though refuses to release control to others (other than the person who signed up for the service). This would extend to domain names, servers, mirrors, etc.
Maybe Leonard offered him a job, or made him an offer, he could not refuse. (joking of course but I’d really hate to see “void-linux a trademark of RHat”).
As they may say in Obarun, c’est la vie
Small reminder here for new Void users.
Void is so strict in minimalism and simplicity that it does not include a system logging system by default. It is directed to experienced linux users who know, value, and want to choose what logging system they like to install and configure it to meet their needs. This is new and refreshing as an approach, even though across the unix/gnu-linux/bsd world there seems to be concensous that some degree of logging is essential if you ever want to troubleshoot just about anything that has gone bad.
Here is what you do. You first look for what is available through void’s repository:
Now that our single Debian person has distanced *self from Devuan (systemd free Debian) and the rest of us made a new Arch person, we must answer a question relating to the discontinuity of Devuan coverage. What is so different in Arch world from the Debian world? Why is this importance in tor/onion networking internal to Debian that is less relevant in Arch? We have identified several attributes that we consider different.