6 ms·
It autodiscovers the dependency chain or shit like that? If you got 500+ services that need to be orchestrated you honestly have a very different problem. I lo
by rootnod3 10mo ago
It autodiscovers the dependency chain or shit like that? If you got 500+ services that need to be orchestrated you honestly have a very different problem.
I love the simplicity of RC scripts. Easy to understand, easy to debug, it just fucking works.
Simplicity is king, because it's understandable. A behemoth like systemd feels like it requires a PhD.
Systemd also runs 100% against the Unix/Linux philosophy of composability and single purpose.
- arthurfirst 10mo agoTHIS ---- Systemd also runs 100% against the Unix/Linux philosophy of composability and single purpose.
- tombert 10mo agoIf you need to make sure that the network stack starts after the usb stack and that starts after the pcie stack and that starts after the … then systemd is considerably easier than SysV init. You’re handwaving away something that is pretty important. You can say that having 500 services is its own problem but it’s also a reality, even on desktop operating systems.
- rootnod3 10mo agoCount how many services you have that are not already defined by the system itself in its order? So, remove core system services. System itself should already make sure that USB starts after PCIE and all that. So go and count all the services that are not base install and tell me how many you have.
- pezezin 10mo agoIn which bizarre world is an RC script easier to understand than a systemd service file? There is nothing simple about RC scripts.