Recently, I noticed something: in the past, tutorials focused on explaining the steps and, eventually, providing a script to launch the software at boot. In recent tutorials, often half of the steps are about integrating with systemd. Are we getting closer to the Windows registry? 😆

#IT #SysAdmin

@stefano no, because #SystemD makes shure that it launches and that yu get proper error and status messages when it doesn't.

#Linux #Sysadmin

@stefano
Aaaaah! I don't want such a situation!😭
I love simplicity of system-wide configurations on *BSD, which looking into /etc/ and /usr/local/etc/ are sufficient.😀

@stefano dont forget #apparmor :P

tbh systemd doesn't scare me too much, but i did try to make a script (booted at launch) provide notifications to the screen like the big tech firewall and i kept getting an error about no access to $DISPLAY and that was a bit bothersome, i haven't gotten around to fixing it yet.... looks to side wryly ....one day.

@stefano

Well, systemd is being developed under microsoft umbrella in the end. So who knows what is their real objective.

I am quite sure in few years, at least some distros, will be seeking way out.

Now the question is - will there be any viable alternatives in existence. Not only init systems but also other unix tools that were murdered by systemd.

We should make tutorials regarding FreeBSD's RC to counter this

@TomAoki @stefano you both should really watch "The tragedy of #SystemD" by #BennoRice because it's good
https://www.youtube.com/watch?v=o_AIw9bGogo

@as400 @stefano Do you have some kind of explanation for the Microsoft link? Yes, systemd used to ba a bit controversial, but it is first time I hear this one...

@as400 like, for example?
@stefano

@fedops
@stefano

Below article presents multiple examples.

https://kevinboone.me/systemd_embedded.html

@pavel
@stefano

Lennart is working for Microsoft.

@as400 @stefano Aha, I had him in "RedHat" box. Updated :-).

@as400 @pavel @stefano Lennart has been working for M$ since at least 2022.

@joel I mean, #SystemD wasn't done by #Poettering because he had no hobbies - far from it.

• #SysVinit sucks and #Linux needs to modernize and change solely because many components like #Xorg, #OSS / #ALSA and #OpenGL are to be retired or are already only on life support.

SystemD, like #Wayland and #PipeWire is a "necessary evil" because the preexisting solutions are slow, not adaptive, cumbersome or just don't work well at all (i.e. mixed (#DPI & #HiDPI) screens with #X11 are just broken!

• People had years if not over a decade to fix those but they didn't and it's clear that a new & clean slate was necessary...

far from being competent enough to either critisize or venerate systemd, i've been curious of gnu shepherd since i've stumbled over itvon news recently… curious enough maybe to even try guix some time soon if only to see how it works.

https://www.gnu.org/software/shepherd/

@kkarhan @joel
A decade or so ago I was anti-systemd but over time I've come to appreciate the design of it. The functional parts and how they fit together and are configured (which are text files, but the names of the configuration keys *make* *sense*) all feel logical and even predictable.

@virtuous_sloth @joel also #SystemD really shines when it comes to #DependencyResolution, enshuring that i.e. httpd only gets launched when mariadb is up and running or similar prerequesites are fulfilled.

And journalctl -xe just makes diagnosing issues superfast...