2009/3/10 Marco d'Itri <md@xxxxxxxx>: > On Mar 10, Nilshar <nilshar@xxxxxxxxx> wrote: > >> For example, if I need to restore a sytem into a vmware, this file >> needs to be changed. on a normal box, udev will add the new interfaces > Every time you change the hardware for a system, even if it is virtual > hardware, you need to delete the file. ok, so deleting it is the good thing to do. it always worked for me with earlier version of udev, good to have a confirmation of that, thanks. > >> as eth2 etc.. so I'll have to delete the file so it will be recreated >> with eth0. How can I do that on a vmware ? > udev will do it if needed, but it's not mandatory to have one (e.g. if > all or your interfaces are handled by the same driver then their names > will usually never change). so, if I got 3 interfaces with the same driver (pcnet32), udev will think it's not needed and will not recreate the file ? Is there a way to force udev to create it ? > > BTW, we are talking about paravirtualized network interfaces. If vmware > is emulating a real interface then there is some other issues. I'm using 3 interface on my vmware, it's emulation of pcnet32 card. see the output from lspci : 00:11.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) 00:12.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) 00:13.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10) > > -- > ciao, > Marco > Thank you Marco. -- 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
