Just when I thought I had gotten udev working right. I just upgraded to udev-118-1.fc8 under the 2.6.24.7-92.fc8 kernel. I have two network interfaces on my box, and they were named eth0 and eth1 as per normal, before I updated. After the update, none of my VMWare virtual machines started without a network error saying that the bridged network device on vmnet0 was down, and the iptables started dropping all packets.
Checking /etc/sysconfig/network-scripts revealed the ifcfg-eth0 had been renamed ifcfg-eth0.bak and two new files, named ifcfg-eth1 and ifcfg-eth2, had been written in it's place. Checking /etc/udev/rules.d/70-persistent-net.rules showed that the interface names had been incremented by one. I tried removing the file and rebooting, but no joy. Same problem. Tried adding a line in 70-persistent-net.rules: SUBSYSTEM=="net", DRIVERS=="forcedeth", NAME="eth0" This didn't work, because restarting udev just caused the file to be rewritten by the /lib/udev/write net rules script. I got the network working again by manually changing all the references it eth0 in iptables to eth1, but doing this in VMWare is a pain. Before I go poking at the udev scripts any more, does anyone have a fix already concocted for this? This nonsense is really frustrating, I was under the impression that udev's purpose was persistent naming, not persistent renaming, of devices. Thanks for any help in advance, Robert Donovan -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
