Slashdot Mirror
Systemd-Free Artix Linux OS is Looking For Packagers (artixlinux.org)
MrBrklyn (Slashdot reader #4,775) writes: Artix Linux, the young systemd free OS based on arch, is reaching a critical point in it's development and calling for new packagers.
Here's more from the ongoing thread on the project's forum: You don't have to be an expert in the occult arts for that; an elementary grasp of Linux in general and how PKGBUILD works should be enough for basic contributions. Help and training will be provided, free of charge!
Here's more from the ongoing thread on the project's forum: You don't have to be an expert in the occult arts for that; an elementary grasp of Linux in general and how PKGBUILD works should be enough for basic contributions. Help and training will be provided, free of charge!
It replaces SysV init.
Basically, SysV init meant there was a lot of duplicated code involved in starting system services, as every service had to write its own SysV init script, and didn't provide a dependency mechanism (this service requires this other service be running first) so that most distros ended up hacking on a solution to provide that. (Basic example is "web server requires network running before it can start.")
systemd solves those problems and then introduces a whole host of brand new problems. Whether or not you want to deal with the brand new problems systemd adds defines whether or not it's "better" than SysV init. It does legitimately solve some issues, but it also makes the boot sequence unpredictable and way more complicated, along with other issues there's no good reason for it to have, like logs that aren't human-readable and moving random system functions into init for no good reason.
Or, in short:
Good idea: replacing SysV init
Bad idea: replacing SysV init with systemd
I had systemd run maybe for a combined 10h so far, in a number of new installations. Nothing but problems. Even the one where I originally thought I could leave it in (Orange Pi zero), it caused serious problems and ripping it just out for sysIV init was far easier than to track down and solve its obscure issues.
It is like Windows: Unless you do exactly what the "developers" ("cretins" would be a more appropriate term...) expect, it falls flat on its face and it is maximally unhelpful when you try to find out what is wrong. That is not anything I will tolerate in a Linux installation.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
The previous standard interactions with init, including the use of shell scripts in /etc/init.d, and the chkconfig and service commands still work. You don't actually need to learn anything new unless you want to take advantage of the new features that systemd offers.
So you might be able to see why your argument rings hollow.
That is not true on both fronts. The standard init stuff does not work with systemd. Not the login scripts, the X scripts, sound scripts, and more.
Secodnly, you do need to learn how systemd does weird stuff, unless you want a system where systemd allows any password to work with sudo - and other weird stuff that has leaked into the distros.
The distros that adopted systemd didn't just keep using the same init scripts. They adapted to it. In order to get around it, everything is affected from udev on up the food chain. The borad change in the distros since adaptation can not be avoided because of a smug comment on slashdot.
http://www.mrbrklyn.com/amsterdam.html http://www.brooklyn-living.com
Artix Linux is an Arch Linux derivative, and it uses the same package system as Arch does. If you want the Debian derivative, that's called Devuan.
Artix
Your Linux, your init.