Systemd is both good and new. Unfortunately what is new is not good, and what is good is not new.The idea behind systemd (even for all the negativity around it) is actually very good.
Systemd is both good and new. Unfortunately what is new is not good, and what is good is not new.The idea behind systemd (even for all the negativity around it) is actually very good.
You can. I was a little bit late, but I updated it in the afternoon IIRC. P.S. Don't forget to click Like @least 3 times in a row, until Trihexagonal's Demonica pops up & dances on your X11 desktop background image.As a lover of BMWs, I can't subscribe to today's BMWs.
Not every Linux init system is bad.FreeBSDs' init system is one of the reasons I switched from linux!
systemd
is pretty bad but for example Void Linux uses runit which is pretty decent.Or, if something misbehaves and you want to have a look to fix itYou don't care about the init system unless you want to tune it according to your own needs.
And there is where systemd can become a pain.
Well, it's not for lack of interest:(Ok, it doesn't have a built-in MP3 player... yet).
I have tried Devaun (which is derived from debian)with openrc, as well as Artix (which is derived from arch) with openrc. Both are good but they all have the drawbacks of being linux making them obviously not FreeBSD. If you've used FreeBSD you most likely will not return to linux.The other distro is devuan, which uses openrc.
You don't care about the init system unless you want to tune it according to your own needs.
And there is where systemd can become a pain.
Careful now, someone might just think to themselves, "what the Unix world really needs is for systemd to be integrated with PulseAudio"...Ok, it doesn't have a built-in MP3 player... yet
s/fire/poetterware/
I'll just put this over here, with the rest … of the fire
Careful now, someone might just think to themselves, "what the Unix world really needs is for systemd to be integrated with PulseAudio"...
Because Poettering didn´t know the difference between an init system and a supervisor. At this point, since systemd is an octopus supposed to do everything, it doesn´t really matter anymore.Second explanation was that it could automatically restart services. Apart from the fact that init and most of its alternatives can do that, that's usually not something you want to do. For example if a database crashes with SIGSEGV, an uncotrolled restart is not very much desireable.
As part of the big plan, since you have more things outside of the systemd that copes with them, such as gnome and everything also entangled with gnome. If you look outside the box, there´s more to come.I think anymore, systemd is already well on the way to being an octopus encompassing everything; they already pushed out the part that now systemd controls your user home directory and does it's own encryption stuff. Eventually, they'll just include their own kernel and lock in everything even more.
Ah yes, amused, the new systemd add-on daemon which will control the flow of humour and entertainment that is permitted on one's system.Well, uhm, LOL.
(please add an "amused" [snip])
They´ll probably create a systemd-nocomplaind so you can´t blame systemd for trashing your system. Also, with a nocomplaind-list.service with a list of words that you can´t use against systemd.Ah yes, amused, the new systemd add-on daemon which will control the flow of humour and entertainment that is permitted on one's system.