This is a MAJOR development with Redhat NO LONGER giving public access to the base RHEL source code. Support My Work-----------------------------------------...
Potentially this means that Fedora and CentOS stream do not get timely updates implemented in RHEL.
Canonical must be throwing a party, and I bet SUSE is not hating it either
systemd is one of the best things that has happened with linux. Instead of random shell scripts that work differently on each distro, now you have a single ini conf file for your service that configures automatic restarts, sandboxing and activation in a easy to use way.
I mean a core issue is that it doesn’t adhere to the unix principle of do one thing and do it well. Aside from that it essentially creates a middle layer where things can happen without you really knowing it’s happening. If you haven’t I’d suggest running a couple of different init systems to see what I mean.
I’m ambivalent, I like systemd because it’s convenient, but I also like openrc because it’s simple.
They see all the other stuff that gets packaged under the systemd name and assume it’s non-optional. While many distributions do, annoyingly, ship the auxiliary packages like resolved by default, they’re not required if you just want to use the init system, and honestly they kind of strike me as an attempt to supplement or replace some of the incumbent components of your average distro.
Systemd-resolved can suck my whole grundle, though.
i see you have not tried to configure and debug dynamic split dns setups that are very common in enterprise vpn world.
before systemd-resolved you had to use dnsmasq running on localhost with bunch of shell scripts to reconfigure it when vpn interfaces come and go for split horizon dns to work propperly.
now with systemd-resolved you can easily tell it what dns prefixes are handeled by what dns server and everything is nicely cleaned up after vpn goes down.
A specific design philosophy that is adhered to means the software has greater interoperability, reliability, and maintainability. When you are criticising something that adheres to a design philosophy, communicate how it’s adhering to that philosophy to it’s own detriment.
systemd is one of the best things that has happened with linux. Instead of random shell scripts that work differently on each distro, now you have a single ini conf file for your service that configures automatic restarts, sandboxing and activation in a easy to use way.
I’m so confused as to why people hate systemd.
I mean a core issue is that it doesn’t adhere to the unix principle of do one thing and do it well. Aside from that it essentially creates a middle layer where things can happen without you really knowing it’s happening. If you haven’t I’d suggest running a couple of different init systems to see what I mean.
I’m ambivalent, I like systemd because it’s convenient, but I also like openrc because it’s simple.
Same here… I like it a lot.
I don’t like systemd. Reasons:
broad scope and lots of dependencies are more or less the exact opposite design philosophy of *nix
putting too many eggs in one basket intrinsically increases the attack vector and also decreases stability
bloated
Most importantly:
And with this news, that last point is what sold it to me
They see all the other stuff that gets packaged under the systemd name and assume it’s non-optional. While many distributions do, annoyingly, ship the auxiliary packages like resolved by default, they’re not required if you just want to use the init system, and honestly they kind of strike me as an attempt to supplement or replace some of the incumbent components of your average distro.
Systemd-resolved can suck my whole grundle, though.
@eltimablo @SmokeInFog @words_number @vegivamp @bigkahuna1986
“Systemd-resolved can suck my whole grundle, though.”
Actual lol, and I agree. I’ve kinda learned to live with it and to most keep it out of the way, but seriously what a pain.
i see you have not tried to configure and debug dynamic split dns setups that are very common in enterprise vpn world.
before systemd-resolved you had to use dnsmasq running on localhost with bunch of shell scripts to reconfigure it when vpn interfaces come and go for split horizon dns to work propperly.
now with systemd-resolved you can easily tell it what dns prefixes are handeled by what dns server and everything is nicely cleaned up after vpn goes down.
deleted by creator
A specific design philosophy that is adhered to means the software has greater interoperability, reliability, and maintainability. When you are criticising something that adheres to a design philosophy, communicate how it’s adhering to that philosophy to it’s own detriment.
And I think it sped up booting a lot too by doing more in parallel.