Have you read @sourav 's article linked in the Newsletter?
One significent paragraph
" Their motivation boils down to upstream changes that left the team in a tight spot. Systemd 254 dropped support for its split /usr setup, later versions killed AUFS compatibility, and KDE Plasma’s increasing systemd dependency made things worse."
It amounts to saying systemd is dictating what distro developers can do.
Some developers value independence , and are switching to other init systems.
Dinit 's commands are similar to systemd commands, and it can perform all the same functions. It is a good choice for KaOS.
Yes. It is centered around Qt and it used to be KDE , but now moved to Wayland and Noctalia.
It is a small little used distro, but it is perhaps a sign of a trend.
We need to get a major distro moving from systemd to either S6 or dinit. Devuan and MX dont count … they are hanging onto old sysvinit.
It is way simpler than S6 to use … you dont write run scripts, you ŵork with a service file that is a simple config file.
Its commands are similar to systemd eg
dinitctl enable ssh
dinitctl status cron
It is not like S6 and runit where you have a supervisor process running for every service, as well as the daemon . It just runs the daemon. … the init process ( called dinit) does all the supervision and logging itself.
From a programmers viewpoint dinit is about 10,000 lines of C++ code … systemd is 1.5 million lines of code. Yet they both have the same functions … dinit can do anything systemd does… but it does not try to do things outside of the init system . It just manages services without growing tentacles elsewhere.
You could drop dinit or s6 into some distro like Ubuntu or Arch, and 90% of users would not notice any difference. I would not expect any user resistance. It is developer resistance and irrational fear of losing market share… and … Redhat have a history of clinging to bad programming because they wrote it.
Of systemd and my objection to it I can refer back to an earlier post I made about Debian 13 and the problem I have faced getting SMB shares to appear on the desktop as they always have in the past prior to Debian 13.
It seems from research I have done that the problem stems from systemd . The issue is still not fully resolved although I did find a workaround which partly solved it. What I’, struggling with now using the GNPOME Extension Network Share Automount is the inability to change the text displayed for the share underneath the desktop icon which insists on displaying the IP address of the SMB share from the NAS which was not a feature of the arrangement prior to the need for this extension only because of the decision to use systemd. I haven’t spun up a copy of Kaos yet, but might just see if that fixes things for me. Will it run in Boxes?
Yes, Artix is Arch based, but its install is as easy as most of the commonly used distros. You have to choose which init system , it offers a choice , I choose dinit.
Artix uses the pacman package system ( not apt). you have to learn that. It is similar to apt, just different commands. If is important with pacman to always upgrade, before you install new packages.
I suggested it because you wanted to try a different init system to see if it would help with your problem. … another option would be Devuan … you might find Devuan easier … it uses apt package system… Devuan’s installer is called Refracta … it is graphical.
This was years ago, but I had Artix with XFCE running (apart from sound, not that I expected that to work out of the box) on an ancient Dell Chromebook 11.
