3 ms·

I maintain pretty tight control over all of my systems. I don't typically want miscellaneous daemons floating around with configs strewn about /etc, so systemd'

I maintain pretty tight control over all of my systems. I don't typically want miscellaneous daemons floating around with configs strewn about /etc, so systemd's ecosystem fits nicely with that. Sure, that's personal preference, but there's something to be said about cohesive system configuration.

bayindirh 2y ago
NM is not a miscellaneous daemon which throws configuration files around. It's under "/etc/NetworkManager" for Debian, and it uses standard sysconfig/network-scripts folder in RedHat. So it's pretty cohesive since it integrates with everything pretty nicely from get go. All the config files are pretty human readable, and there are tons of tools plus your favorite editor to work with it. Of course you can prefer to use the tools from the same toolbox, it's your system, it's your choice. However, my experience shows me that using full-featured stacks even if they are not that tightly integrated is better in the long run. E.g. I used to use DHCP options in my home network in the past, and we use them at work. So even if systemd-networkd feels good, it means nothing if I can't configure my system the way it should be. When I have thousand servers to tend, I want my configs to work the way they should. I can't get emotional about how using all my tools from a single toolbox, or this and that. I just want my systems installed, work reliably over long periods of time, and just sleep at night. Network manager proved to be both helpful and reliable in that regard, so I'm a happy camper.
- packetlost 2y ago
  Good to hear! I'm glad NM (and other tools) exist, and I'm not saying they shouldn't. My needs are adequately met by the tools systemd-networkd provides, and I find it works well. Again, it's optional. I also wasn't really referring to NM itself, but about other ancillary daemons that were referenced in the GP.
throw0101d 2y ago
> I don't typically want miscellaneous daemons floating around with configs strewn about /etc, so systemd's ecosystem fits nicely with that. Ironically resolved running is another miscellaneous daemon, and it messing around with /etc/resolv.conf makes systemd's ecosystem super annoying to me.

bayindirh 2y ago

NM is not a miscellaneous daemon which throws configuration files around. It's under "/etc/NetworkManager" for Debian, and it uses standard sysconfig/network-scripts folder in RedHat. So it's pretty cohesive since it integrates with everything pretty nicely from get go. All the config files are pretty human readable, and there are tons of tools plus your favorite editor to work with it. Of course you can prefer to use the tools from the same toolbox, it's your system, it's your choice. However, my experience shows me that using full-featured stacks even if they are not that tightly integrated is better in the long run. E.g. I used to use DHCP options in my home network in the past, and we use them at work. So even if systemd-networkd feels good, it means nothing if I can't configure my system the way it should be. When I have thousand servers to tend, I want my configs to work the way they should. I can't get emotional about how using all my tools from a single toolbox, or this and that. I just want my systems installed, work reliably over long periods of time, and just sleep at night. Network manager proved to be both helpful and reliable in that regard, so I'm a happy camper.

packetlost 2y ago
Good to hear! I'm glad NM (and other tools) exist, and I'm not saying they shouldn't. My needs are adequately met by the tools systemd-networkd provides, and I find it works well. Again, it's optional. I also wasn't really referring to NM itself, but about other ancillary daemons that were referenced in the GP.

throw0101d 2y ago

> I don't typically want miscellaneous daemons floating around with configs strewn about /etc, so systemd's ecosystem fits nicely with that. Ironically resolved running is another miscellaneous daemon, and it messing around with /etc/resolv.conf makes systemd's ecosystem super annoying to me.