I guess I misunderstood your comment. IMO, bug #90681 has no relationship to NetworkManager at all. It could be that the system in 90681 has disabled NetworkManager altogether and is using raw dhclient; that bug would still happen. The problem that the dhclient-script overwrites /etc/resolv.conf and deletes changes put there by other software such as VPN startup won't be solved by a dhclient that works with NetworkManager... it will only be solved if all the "other software" in question is ALSO changed to use NetworkManager.
That is NOT going to happen. Expecting it to happen is naive. Saying that until it does happen your system is going to break and that's just too bad for you is bad policy. This is why I hate NetworkManager. It, or at least the way it's implemented in Ubuntu, is just a fundamentally WRONG way to solve the very real problems we have. The idea that NetworkManager owns every aspect of every networking capability on the system and that in order for things to work properly everything has to be REWRITTEN to use NetworkManager instead of whatever method that software has been using for 30 years across 25 other versions of UNIX is not a solution, it's a cop-out. It's quite simply a bad design decision and it's taking Ubuntu in the wrong direction. But, that's a rant for another bug report. -- dhclient updates resolv.conf behind network-manager's back https://bugs.launchpad.net/bugs/192566 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
