2 ms·
> some systemd subsystem wedged during the upgrade. Now networking is broken. All software has problems. Without specific details, blaming your problem on sys
by teddyh 6y ago
> some systemd subsystem wedged during the upgrade. Now networking is broken.
All software has problems. Without specific details, blaming your problem on systemd specifically seems just as unreasonable as blaming “Linux” or even “Unix”. In fact, in past years during the old OS wars, there were many such rants, blaming “Unix”. (See for instance The Unix-Haters Handbook.) Become a curmudgeon, and idolize the past, at your own peril.
I recommend, instead, to live in the present, to use currently normal software, and to fix every problem as it appears. Ceasing to upgrade permanently (possibly by moving to an obviously dead-end fork) is never a sensible option in the long run.
- mumblemumble 6y agoDon't bring the Unix-Haters Handbook into this. A fun, self-consciously curmudgeonly romp like that has about as much in common with the systemd debate as P.J. O'Rourke does with Bill O'Reilly.
- teddyh 6y agoI don’t know who any of those people are.
- flohofwoe 6y agoI think the point of the parent was that systemd will be much harder to replace than other init mechanisms once something better comes along, because it grows into every part of a Linux setup. And if that's true, then systemd actually hinders progress and innovation, because the cost of replacement will be too high.
- teddyh 6y agoPossibly, but that was not the part which I chose to comment.