5 ms·
What exactly is "garbage" about this? It's so tiring how systemd opponents insist on name-calling instead of substantiated criticism. There is no reason every
by 9dev 3y ago
What exactly is "garbage" about this? It's so tiring how systemd opponents insist on name-calling instead of substantiated criticism.
There is no reason every single application should manage network socket acquisition on its own - I'm not very fond of the times everyone and their mother wrote whacky shell scripts to start and stop their services, either. But somehow those seem to be the "good old times" you guys miss.
- all2 3y agoI don't think its a systemD thing. This sounds more like an issue with changing a server's behaviour without asking.
- 9dev 3y agoDistribution upgrades have never been an unobtrusive thing. Despite this, everything will continue working exactly as configured before the upgrade, which applies new configuration recommendations by the vendor. What is wrong with that?
- all2 3y agoWhat's wrong is the config file moved. If a sysadmin is used to a config file being somewhere they know, and then it disappears that can be extremely frustrating. Especially on a production system.
- 9dev 3y agoWhich the sysadmin knows, because they reviewed the changelog for the major system upgrade they just did. You wouldn’t install a new major version of a database without any precautions either, right?