On a related note, rerunning kudzu SEEMS to fix this problem which leads me to my next question, is it possible to run kudzu --quiet so it completes without interaction? I have not done that in fc2... Thanks again Michael Weiner -----Original Message----- From: MW Mike Weiner (5028) Sent: Thursday, January 12, 2006 12:00 PM To: 'For users of Fedora Core releases' Cc: MW Mike Weiner (5028) Subject: network interface not starting on reboot Importance: High This is odd, i have 125 FC2 servers being racked and stacked today in my data center, and interestingly enough it seems eth0 is failing to start on bootup. I checked the following: /etc/modprobe.com (alias eth0 e100, is present) /etc/sysconfig/hwconfig (stanza for the e100/eth0 device is present) /etc/sysconfig/network (set to start on reboot) /etc/sysconfig/networking/devices/eth0 (exists) /etc/sysconfig/network-scripts/ifcfg-eth0 (exists and in correct format as far as I can tell) and it just refuses to start on a reboot. Is there a fairly simple fix? I am trying to fix these remotely, so i dont have console access at the moment. I can however, get to the back interface (eth1) on a reboot, so i CAN still get to the box, but i need both to come up on a restart. Thanks in advance for any insights. Michael Weiner
