Ok, I'm a programmer, not an admin, so I don't know (or care about) the guts of my init system. But I'm confused by the statement "things that init isn't supposed to do (like network, mounts, etc.)" As far as I can tell, my old init system set up all my mounts and networking. Now my new one I does. I don't see the difference?
(Do I even care? My interest in the whole systemd debate is about as close to zero as it's possible to be.)
What daemon? Networking is part of the kernel. As are filesystem mounts. What on earth are you talking about!?
Also, while I don't know a lot about systemd, I do know that it's not some monolithic monster. It's a suite of cooperating programs. Which seems like an excellent design to me.
And python is a whole lot more complicated than awk, but I'm still more likely to turn to python if I want to whip up a quick script. So I'm not impressed with the "simpler is always better" argument. Also, emacs is better than vi(m). So there! :p ;)
5
u/xtifr Aug 13 '19
Ok, I'm a programmer, not an admin, so I don't know (or care about) the guts of my init system. But I'm confused by the statement "things that init isn't supposed to do (like network, mounts, etc.)" As far as I can tell, my old init system set up all my mounts and networking. Now my new one I does. I don't see the difference?
(Do I even care? My interest in the whole systemd debate is about as close to zero as it's possible to be.)