Description of problem: When installing fedora 9 through anaconda, a user get the opportunity to assign a static IP/dns settings. Upon first boot, NetworkManager clobbers these settings How reproducible: Always Actual results: /etc/resolv.conf is replaced with the line: # generated by NetworkManager, do not edit! Expected results: NetworkManager either be 1. disabled if someone enters a static IP 2. be smart enough not to remove dns settings created by anaconda (ignore the resolv.conf all together, if there are settings that it didn't create in there). It seems kind of silly to assign the system dns settings, when NW manager is just going to delete them. Workaround: create a %post anaconda directive, or switch to vt2 before restarting, and run: chkconfig NetworkManager --level 35 off chkconfig NetworkManagerDispatcher --level 35 off
You'll want to put the DNS settings into the ifcfg file directly, as: DNS1=xxx.xxx.xxx.xxx DNS2=xxx.xxx.xxx.xxx for the moment, the GUI config tools don't do this though fixes are planned...
*** This bug has been marked as a duplicate of 443244 ***