On Mon, 2006-12-11 at 12:35 -0600, Marc Schwartz wrote: > On Mon, 2006-12-11 at 12:12 -0500, Matthew Saltzman wrote: > > On Mon, 11 Dec 2006, Marc Schwartz wrote: > > > > > Aaron Konstam wrote: > > >> On Mon, 2006-12-11 at 09:42 -0500, Gene Poole wrote: > > >>> Beware - It seems that the first time you use NetworkManager it destroys > > >>> the contents of you resolv.conf (built at install time). It also seems > > >>> that it doesn't make a backup copy first. > > >>> > > >>> Thanks, > > >>> Gene Poole > > >>> > > >> I have never noticed that this is true. I will have to look into your > > >> statement. > > > > > > If you have a network profile that is based upon a fixed IP address and DNS > > > servers (which I do have at home behind a router with DHCP disabled), then NM > > > will overwrite the configurations for that profile, including > > > /etc/resolv.conf. > > > > > > Have you tried using "system-config-network-cmd --profile profilename --activate"? If you have two profiles, one that is activated when you boot your system wanting NM (only lo adapter is activated, all others are "ONBOOT=no"), the other has your Ethernet adapter turned on and "different DNS settings".... Then if you activate the profile with the above command (rather than "ifup eth0"), it should copy in the new settings. Also, take a look at the "netprofile=profilename" kernel argument, that can reset your system back to the NM profile by default every time you boot..... --Rob -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
