A while ago, an Obarun user, Dr Saleem Khan (1) urged me to try Spark Linux and it was the first time I heard of it. It must have been during some real busy period and it was since forgotten. While I was trying to clean up the list of linux distributions without systemd the name came up again. Thanks, Saleem.
By no means do I think this is for entry level users to try as a distribution with a full desktop, but for minimalists who are accustomed to arch this is an exercise of how minimal can you get with a ready off the shelf arch base on which you can build from ground up.
The project is severely undocumented, although there is not much to document for an experienced user. Spark (by Jack L. Frost) uses sinit as its init system and ssm which is an inhouse Simple Service Manager by Spark founder.
Sinit according to its source suckless (they suck less) is:
sinit – suckless init
sinit is a suckless init, initially based on Rich Felker’s minimal init.
sinit is considered complete and no further development is expected to happen.
Relevant links sinit + daemontools-encore
sinit was created by Dimitris Papastamos and was “finished” in 2015, that I believe is a year after runit was finished as a frame of reference.
How can someone here, defend Void’s honor from a tremendously sloppy and unjustified criticism by the corporate rag (as in the piece of cloth used to wipe genitals after corporations take a crap, and they do all the time, especially on May Day and when strikes and mass protests are taking place around their headquarters) “distrowatch” …. and the very next day attack void as being the worst form of malware that has hit the open and free software world?
Basically we are not a “fan club”, defending anyone as being god, or hating someone as being the antigod. Criticism, for those that understand the term within rational thinking, has to and must be objective, to the best reasonable effort (that is all we human can do). Only then can there be a dialectical agreement about reality, our best interpretation of it. Despite of how many of you here, feel like they are finding a home at this systemd hate club of hooligans, enjoying braking knee caps of their opponents. No, it is all objective criticism at something that is gradually becoming a “social danger”. It is the Trojan Horse (and damn the damn Greeks for inventing this strategy to defeat the peace-loving Thracians and take over their land and resources, which they did, that is not Homer’s mythology but a historic fact) that is used by mega corporations to swallow and end this industry of open and free software, running on non-open and non-free hardware in lack of an alternative, which should be a social goal. In this respect open and free software is an industry from those below against the interests of those above, a miracle or a mistake by those that rule and dominate.
Trident project released a beta image following their alpha releases in the past two months.
For those who missed this developing transition, of Trident leaving its TrueOS/FreeBSD base and moving to linux using Void as its base, here is a summary of what you are missing. It has been a common story for a distribution being fed-up with linux development, developers being consumed to modify their software around systemd-functionality, and have moved to some form of a BSD-unix base. As far as we know there hasn’t been an effort to leave BSD to come to linux. So Trident is drawing its own path making it now a 2 way street. Here are a couple of juicy quotes of their late announcements:
…Currently, Project Trident is based on FreeBSD and uses the TrueOS build framework. Over the years, we have accumulated multiple long-standing issues with the underlying FreeBSD OS. Issues with hardware compatibility, communications standards, or package availability continue to limit Project Trident users…..
1st some history/background:
Back some time ago an alternative to sysvinit was developed called daemontools (look at sources below) and people liked it. From “it” runit was cloned, very similar but started from scratch, to be as small, as light, as simple, and as responsive as hw itself. Runit set some goals for its development, kept being refined and eliminating any bugs, it worked on as many architectures as people could get their hands on, and the chief runit man decided to put it to bed. Runit has been frozen in time by its developer. Don’t expect it to catch up with other system development unless Void decides to clone it and develop it on their own, which in some ways they already do, but it is more polishing up the existing runit.
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
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-22.214.171.124_1 Small suite of programs for UNIX, designed to allow process supervi...
[-] s6-devel-126.96.36.199_1 s6 supervision library and headers
[-] s6-dns-188.8.131.52_2 Suite of DNS client programs and libraries for Unix systems
[-] s6-dns-devel-184.108.40.206_2 Suite of DNS client programs and libraries for Unix systems - devel...
[-] s6-dns-doc-220.127.116.11_2 Suite of DNS client programs and libraries for Unix systems - docum...
[-] s6-doc-18.104.22.168_1 s6 supervision documentation
[-] s6-linux-utils-22.214.171.124_1 Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e...
[-] s6-linux-utils-doc-126.96.36.199_1 Minimalistic Linux-specific system utilities (s6-chroot, s6-mount e...
[-] s6-networking-188.8.131.52_1 Suite of small network utilities for Unix systems
[-] s6-networking-devel-184.108.40.206_1 Suite of small network utilities for Unix systems - development files
[-] s6-networking-doc-220.127.116.11_1 Suite of small network utilities for Unix systems - documentation
[-] s6-portable-utils-18.104.22.168_2 Tiny portable generic utilities (s6-cat, s6-chmod, etc.)
[-] s6-portable-utils-doc-22.214.171.124_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