On Wed, May 21, 2008 at 2:24 PM, Robert Donovan <[EMAIL PROTECTED]> wrote: > On Wed, May 21, 2008 at 1:49 PM, Doug LaRue <[EMAIL PROTECTED]> wrote: >> ** Reply to message from "Robert Donovan" <[EMAIL PROTECTED]> on Wed, 21 >> May 2008 13:37:57 -0700 >> >>> I, therefore, still maintain that udev has lost it's mind. >> >> Were you running VMware when you updated udev? I'm wondering if the >> installation could not free /dev/eth0 because vmnet0 was bound to it >> so it was forced to use the next available device identifiers, eth1, eth2. >> >> Doug > > Hmm, good point, I hadn't considered that. The vmware console was shut > down, but the service was running. I'll check it out. >
Well, I just finished checking it out reinstalled Fedora 8 from DVD and did the updates before installing VMWare. Same results. It seems to be udev that is messing things up, not the kernel or VMWare. Furthermore, I went to NCAS and performed the same experiment on one of the school machines. Again, same results. Upon updating to udev-118-1.fc8, the ethernet device names were all incremented by one. No other devices were being used for network access. Whatever was done to it between 116 and 118, it's not working right. Robert Donovan -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
