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!
That's a weird way to say "There aren't really that many developers or other technically skilled users who don't want systemd."
I don't agree that replacing sysIV init is a good idea. All the arguments for that boil down to "not invented here".
Why is it that so many tech people cannot let things that work well the fuck alone?
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Around 2014, with the switch to Systemd, Debian started to decline in popularity. This was followed by the equally stunning change in Ubuntu to the same init system. By 2018, it was apparent that both distributions were headed to the scrap heap of history as they had lost nearly 80% of their user base in the 3 intervening years.
Oh, wait, that didn't actually happen? Debian/Ubuntu still has the same userbase in the Linux Desktop and Server markets it had before the Systemd change?
I guess the markets have spoken, and the predictions of doomsday were nothing more than the echo chamber effect of a very small and very vocal minority of people who do not appear to represent either Linux users or Linux developers as a whole. That is the only explanation that fits the facts.
I wish I had a good sig, but all the good ones are copyrighted
SysVInit worked fine for me, and no it doesn't boot slower. See what systemD does if you've got stuff waiting for network and for whatever reason there's no network or it's flakey. No warning at all - just no boot, or eventually a boot with no warning. .share way.
Why do I have to learn it's log and status tools after already having had to learn the other way of just using a text editor and knowing some filenames? I have other stuff to learn.
How helpful.
See what systemd does about share mounting in fstab or even the
Why guess when you can know? Measure!
I don't agree that replacing sysIV init is a good idea. All the arguments for that boil down to "not invented here".
Why is it that so many tech people cannot let things that work well the fuck alone?
+1 Wish I had mod points for that. It seems like so many people think mature software is bad or something. Sure, Sys-init/Upstart/whatever had its issues at times (and usually in very small ways), but there were solutions to those warts; it's just that no one really put all the parts together, or so it seems to me.
I've had Systemd fail me in mysterious ways where the system refused to come up (1 I never figured out and solved by backing Systemd out), but I've never had Sys-init/Upstart/whatever fail to boot far enough I couldn't do something with it (and it fails me even in tiny ways so infrequently it's been years since that happened).
To me as a *user*, Systemd feels like a solution in search of a problem. I know the distro/package maintainers like it because it creates less work for them, but I think this is a case where the distro/package maintainers have forgotten at least 1 of their goals: to make it easier on the user.
The original purpose of systemd was to replace System V init.
They did replace System V init, in a very non-Unix-like way, with a monolithic blob full of binary interfaces, Windows-style.
They then continued to merge in more and more stuff, like a friggin DNS server. Had they stopped before replacing Network Manager with yet another integrated blob, systemd would just be a poorly thought out init system which is the opposite of the UNIX way of doing things. Since they didn't stop, but rather continue to merge more and more unrelated stuff, it's a real problem.
like when you're database is turned off by a failed webserver
I'm not talking about dependencies, I'm talking about process groups. Your database is almost certainly not started by your web server, or by the web server service. It's not part of the same process group.
I'm starting to get the impression that you don't understand how these things work.