2 ms·

> For example, Linux DNS resolution is an arcane mess of upstream components bodged together over decades, about the place where sysvinit was before systemd cam

> For example, Linux DNS resolution is an arcane mess of upstream components bodged together over decades, about the place where sysvinit was before systemd came along. Systemd has fixed this as well. Using systemd's networking stack DNS becomes completely seamless with the rest of the system. It's not quite 100% baked for average desktop users, but all the components are there and work great. You'll see distros switching to it soon... particularly workstation oriented ones as the wifi stack is soooo much nicer.

hiram112 7y ago
Does this do away with Network Manager, or do they somehow play nicely together. Part of the reason why I've begun to dislike Linux is that things like networking used to be completely defined in config files, operated on by known commands. Now it just seems like a hodgepodge of a dozen different daemons and applications writing over files, I honestly can't keep track of which is the authoritative config or app for interfaces, DNS, wifi, etc.
- eikenberry 7y ago
  It can do away with NetworkManager or it can work with it. The integration with NM wasn't quite there in time for Debian Buster (which I use) but it was close and might be there now. They were working on it. I have never used NetworkManager so can't comment intelligently on it. But I have it setup without it and it requires just a few config files. How many/how much config depends on how much you want to tweak things and how you want to organize things. The main thing missing in the current stack is a nice interface for wifi. Using iwd for wifi has made things much better and if you don't mind CLI management it is quite nice. For a bit more concrete of an example here is a gist I through up a while back describing replacing the old setup with a systemd based one. https://gist.github.com/eikenb/1e9faeb8210e639e8caa69e9832db594 https://gist.github.com/eikenb/1e9faeb8210e639e8caa69e9832db...

hiram112 7y ago

Does this do away with Network Manager, or do they somehow play nicely together. Part of the reason why I've begun to dislike Linux is that things like networking used to be completely defined in config files, operated on by known commands. Now it just seems like a hodgepodge of a dozen different daemons and applications writing over files, I honestly can't keep track of which is the authoritative config or app for interfaces, DNS, wifi, etc.

eikenberry 7y ago
It can do away with NetworkManager or it can work with it. The integration with NM wasn't quite there in time for Debian Buster (which I use) but it was close and might be there now. They were working on it. I have never used NetworkManager so can't comment intelligently on it. But I have it setup without it and it requires just a few config files. How many/how much config depends on how much you want to tweak things and how you want to organize things. The main thing missing in the current stack is a nice interface for wifi. Using iwd for wifi has made things much better and if you don't mind CLI management it is quite nice. For a bit more concrete of an example here is a gist I through up a while back describing replacing the old setup with a systemd based one. https://gist.github.com/eikenb/1e9faeb8210e639e8caa69e9832db594 https://gist.github.com/eikenb/1e9faeb8210e639e8caa69e9832db...