On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
1) Not to go back to the old ways 2) Find out if any fixes to NM were known of that will fix this
Fortunately the /etc/resolv.conf file itself on SUSE contains generated comments telling you exactly how to fix it the "official" way. So SUSE are idiots for checking for an error they can't handle, but they are geniuses for actually putting the information you are gonna want to know right in the resolv.conf file instead of just leaving you hopelessly lost.
Nice... That would have saved me a couple of hours of googling.
Cheers,
Chris
-- ================================== By all means marry; If you get a good wife, you'll be happy. If you get a bad one, you'll become a philosopher.
--Socrates