I have a strange problem of connectivity in fedora 8, as the system boots up the network is not started.
Supporting Logs

Mar 29 19:59:47 testing1 NetworkManager: <info> Bringing up device eth0
Mar 29 19:59:47 testing1 kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 29 19:59:47 testing1 avahi-daemon[1727]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.119.54.
Mar 29 19:59:47 testing1 avahi-daemon[1727]: New relevant interface eth0.IPv4 for mDNS.
Mar 29 19:59:47 testing1 avahi-daemon[1727]: Registering new address record for 192.168.119.54 on eth0.IPv4.
Mar 29 19:59:47 testing1 NetworkManager: <info> Deactivating device eth0.
Mar 29 19:59:47 testing1 avahi-daemon[1727]: Withdrawing address record for 192.
168.119.54 on eth0.
Mar 29 19:59:47 testing1 avahi-daemon[1727]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.119.54.
Mar 29 19:59:47 testing1 avahi-daemon[1727]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 29 19:59:51 testing1 NetworkManager: <info> Trying to start the supplicant...
Mar 29 19:59:51 testing1 NetworkManager: <info> (eth0) supplicant interface is now in state 1 (from 0).
Mar 29 19:59:51 testing1 NetworkManager: <info> (eth0) supplicant interface is now in state 2 (from 1).

Interestingly If I start the network manually it starts up

Logs
Mar 29 20:23:05 testing1 kernel: IPv6 over IPv4 tunneling driver
Mar 29 20:23:05 testing1 kernel: sit0: Disabled Privacy Extensions
Mar 29 20:23:07 testing1 kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 29 20:23:08 testing1 avahi-daemon[1727]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.119.54.
Mar 29 20:23:08 testing1 avahi-daemon[1727]: New relevant interface eth0.IPv4 for mDNS.
Mar 29 20:23:08 testing1 avahi-daemon[1727]: Registering new address record for 192.168.119.54 on eth0.IPv4.
Mar 29 20:23:08 testing1 avahi-daemon[1727]: Registering new address record for fe80::a00:27ff:fe85:214a on eth0.*

chkconfig --list network says

chkconfig --list network
network 0 off 1 off 2 on 3 on 4 on 5 on 6 off

Anyone

besides that fedora 8 is 8 versions OUT OF DATE and has had NO security updates in 3 years and went END OF LIFE in Jan 2009

it has been unsupported for 3 years now
fedora 16 is current


as i recall fedora 8 had a mess of bugs ,some of them even carried over to fedora 9 & 10
pulse audio was one
ipv4 and ipv6 was a BIG bug
if ipv6 was not disabled during install then it was near impossible to get the network to connect for some ( ISP issues)

also the change from "Network" to "NetworkManager"
THAT was a mess

bugs
http://www.redhat.com/archives/rhl-d.../msg00201.html
also fedora 8 is SO OLD that there is NO SUPPORT FOR ANY NEW HARDWARE

Actually, it was the state of F8 that finally got me around to switching to Centos instead.
I'd been meaning to do it for a while, but that forced my hand ... & I'm glad actually; I wouldn't go back.

Fedora IS GOOD for some things
and VERY bad for others


use what is appropriate for the situation
RHEL/CentOS or fedora


I liked fedora because it required me to "look under the hood and get my hands dirty and greasy " to fix things
fedora 4 to 10 were defiantly a F.O.R.D. ( Fix Or Repair Dally )