Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Instead you edit either one of the interface configuration files and tell NM (via nmcli) to reload it

Yeah, and this would be fine if both /etc/resolv.conf told you what is creating that file and NM didn't rewrite its own configuration files all the time.

Anyway, it would be not that bad if NM was kept restricted to RedHat, because the entire philosophy of that distro is that configuration files are just suggestions and the system is free to change anything at any time. But instead, that behavior infected everything.



The first line of resolv.conf is a comment indicating it's written by Network Manager. So that part didn't trip me up at least.


On Debian it only says it's auto-generated and you shouldn't edit. It's not necessarily created by NM either¹, so it would be really helpful to have it.

1 - The policy of whatever configures your network last rewrites this file is spreading. Apparently systemd creates it first, and Debian has more than one network configurator for you to choose.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: