Public bug reported:
My brawny workstation is both a server and a workstation, so I've had to
manually configure static IP, KVM-support, etc. I keep forgetting that
every time I upgrade Ubuntu, some of my network configuration gets
trashed by network-managers insistent disregard for the pre-existing
configuration files. /etc/resolv.conf seems to be the first and most-
obvious victim.
Typically, the solution is apt-get remove --purge network-manager. Every time
I upgrade, I seem to re-learn this
lesson. So this time, I tried to find a way to live with network-manager's
autocratic ways.
However, editing /etc/dhcp/dhclient.conf to prepend proper DNS
nameservers (and to elide the request for dns nameservers to the local
dhcpd) did NOT convince network manager to stop truncating
/etc/resolv.conf upon either service network-manager restart or reboot.
Googling uncovered other victims of network-manager being re-introduced
by an Ubuntu 11.10 upgrade. However, there still does not seem to be
anyway to get along with network-manager. I'm not keen on deviating so
much from the Ubuntu fold. I'd rather not apt-get remove a standard
application. From experience, I can predict that this will just keep
whacking me - upon each upgrade. Isn't there some way to convince
network-manager to respect manually-set networking configuration files.
I am deeply disturbed by the loss of configuration file primacy. Surely
the files should trump the 'app' - and not the other way around. Yes?
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878390
Title:
Ubuntu 11.10 upgrade kills /etc/resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/878390/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
