I still don't follow. There were no significant changes to how NM handles /etc/resolv.conf from the version in 12.04 to the version in 12.10; and certainly nothing that would cause things to be handled differently if /etc/resolv.conf is not a symlink or is absent.
The IP address change has no impact to this -- if people decided to break their setup by making resolv.conf a standard file, by removing it or otherwise, we should also be respectful of *that* and ultimately not revert their changes (which may or may not have been done for a good reason). Can you further explain what you mean? Provide an example setup, or even a patch? However, there really *should not be* any such changes to the postinst or any NM maintainer scripts to touch /etc/resolv.conf; it's just not the right place to do these things. Instead, if we need to cover an extra case where NM is failing to do the right thing, that fix can go in src/dns-manager/nm-dns-manager.c or one of the other source files in that directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060200 Title: Detect in the postinst that resolvconf is installed but /etc/resolv.conf is not a symlink to ../run/resolvconf/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1060200/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
