[deleted]Submitted 6 days ago by lemming741@lemmy.world to selfhosted@lemmy.world
If you’re not fond of manipulating config files manually, just use nmcli (from your link):
You can get an idea of NetworkManager’s settings by running
nmclion the command line.
It is a bunch simpler. The days of just raw-dogging resolve.conf and nsswitch are long behind us.
Aren’t these docs an admission that it’s a clusterfuck?
The Debian wiki admittedly needs work, but it is a wiki, so make an account and update what you think is lacking or unclear.
These are server VMs. I gave up and did chattr +i and it does what I tell it to now.
From my /etc/resolv.conf on Debian trixie, which isn’t using openresolv:
# Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink.
I mean, if you want to just write a static resolv.conf, I don’t think that you normally need to have it flagged immutable. You just put the text file you want in place of the symlink.
IMO this is largely Debian-specific: this distro seems to hold backward comaptibility in very high regard, so any problem is bound to have a multitude of solutions. In addition, the Debian Wiki is not as well maintained as you-know-whose.
I see nothing untoward here.
Except maybe that last sentence, what “s” are you talking about (fwiw, the man page that comes with an installed package should™ be the ultimate authority)?
dhcpcd overwrites is. I only have one static address, but DHCP does other stuff too it seems
rtxn@lemmy.world 6 days ago
Interface configuration and DNS resolution are managed by different systems. Their file structures are different.