Thanks for your answer Kay, on my vmware system I got : lrwxrwxrwx 1 root root 0 Mar 10 17:04 /sys/class/net/eth0/device -> ../../../devices/pci0000:00/0000:00:11.0 lrwxrwxrwx 1 root root 0 Mar 10 17:04 /sys/devices/pci0000:00/0000:00:11.0/driver -> ../../../bus/pci/drivers/pcnet32 lrwxrwxrwx 1 root root 0 Mar 10 17:13 /sys/devices/pci0000:00/0000:00:11.0/net:eth0 -> ../../../class/net/eth0 so it seems ok... 2009/3/10 Kay Sievers <kay.sievers@xxxxxxxx>: > On Tue, Mar 10, 2009 at 17:48, Nilshar <nilshar@xxxxxxxxx> wrote: >> My problem is on a debian 5.0 (Lenny) with udev version 0.125-7. >> on previous versions of debian, I often deleted the file >> /etc/udev/rules.d/z25-persistent-net.rules, and this file was >> recreated after a reboot. >> I tried to do same thing with Lenny. >> First, I saw that name of this file changed to >> /etc/udev/rules.d/70-persistent-net.rules, si I deleted that file, but >> after a reboot, it was not created. >> After several hours searching the internet, I found nothing solving >> this problem. >> And after more tries, I noticed this only appear on a vmware system. >> Recreating the file /etc/udev/rules.d/70-persistent-net.rules on a >> "normal" Dell server is working just fine. > > It might be, that the vmware interface does not trigger the creation > of a persistent rule. Network interfaces need to be created by a > "driver", be backed by a "bus". > > Look a the devpath of the device and it will tell you the parent devices: > /sys/class/net/eth0 -> ../../devices/pci0000:00/[...]/net/eth0 > which means, that it's backed by a PCI device, and therefore a rule > will be created. Maybe the vmware interface is a virtual one. > > Kay > -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
