If you login the first time in the new installed system do the following as root:
# chkconfig NetworkManager off # chkconfig network on After a reboot the network should come up as expected. Koos. David G. Mackay schreef:
On Thu, 2008-10-09 at 10:30 +0200, David Jansen wrote:Similar to bugzilla #392021 and #374271 I guess, has been this way since Fedora 8. We use static ip addresses here as well, but I had to set up a dhcp server to hand out those same addresses based on mac address, just to make installs work. Quite a pain, and it would be good to get the old, correct behaviour back (Fedora <= 7 worked fine, and so does RHEL 4 & 5), ie: anaconda should do what the user (or kickstart file) tells it to do, and not force dhcp on everyone.FWIW, I've installed F9 on several machines using dvd on some and network install on others without a problem. It's the use of NetworkManager in Anaconda that's causing the trouble. I was hoping for a workaround. I also hope that this will be resolved by the full release. Dave
begin:vcard fn:A.J. Werkman n:Werkman;A.J. org:Digifarma BV adr:;;Postbus 36;Tholen;;4690 AA;Nederland email;internet:AJ.Werkman@xxxxxxxxxxxx title:Drs x-mozilla-html:FALSE url:http://www.digifarma.nl/ version:2.1 end:vcard
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
