On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote: > The only solution I have found so far is to: > 1) properly re-create /etc/resolv.conf to what it should be > 2) 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 have had to use the chattr thing as the best I could find on various different flavors of linux distributions. I've been doing battle with a host of virtual machines we use for testing software on different distros, and to get networking up and NFS filesystems mounted on all of them at boot time has been like herding cats - every one of them has some different quirk to work around. The most interesting was openSUSE - if you try the chattr trick there, the whole boot comes to a screeching halt and it prints a console message saying "Oh No! I can't screw up your /etc/resolv.conf file, what should I do?" 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. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
