Indeed, resolvconf doesn't appear to work properly here either, so cases with one or more devices unmanaged and some devices managed by NM fails -- there's just no easy way to know what to do with resolv.conf in such a case, even just saving on startup and restoring that file on stop is kind of clumsy; this case is really supposed to be covered by resolvconf -- I'll file a separate bug for that.
As for the case with NM installed (read: running) but not managing any devices, it really shouldn't be clobbering /etc/resolv.conf. Fortunately, that's relatively easy to fix. I'll upload an updated package that covers this shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862134 Title: Upgrade to oneiric wiped my resolv.conf for static interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/862134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
