Gaël Lams skrev:
Hi
Aaah.. I missed the 9.3 part.. :) The file I referred to is in v10. Anyway, you can actually rename the file ifcfg-xxxxx to ifcfg-eth0 in your /etc/sysconfig/network directory.
I believe I've seen some posts about it on the VMware forums, but unfortunately I can't recall where or what.. But it had some relevance if I'm not mistaken.
Actually I already tried calling it ifcfg-eth0 and this way the configuration is found and ifconfig gives the "good" answer and when I start /etc/init.d/network the status for eth0 is a "done" but ... I cannot communicate with nothing, the ping gives me network unreachable (and it's not a firewall problem because there is no firewall inbetween).
That's why I was trying to understand how the whole hotplud/udev/network stuff was working. Actually I will probably try to add the persistent_name file in rules.d to see whether it works this way.
But, even not taking into account my problem with vmware, I'm still curious regarding these two points: - how the ifcfg-xxxxx is "mapped" to eth0 because I still don't understand. I can see that the link from /sys/class/net/eth0/ to ../../../devices/pci0000:00/0000:00:11.0 is missing, but I don't understand what makes this link being created - why there are still all the devices defined in /dev if, wiith udeh/hotplug, ony the existing devices should be created
Well, there are some interesting reading in /usr/share/doc/packages/udev and /usr/share/doc/packages/sysconfig In the latter one (on my 10.0) there's even a README.Persistent_Interface_Names which possibly can help you.. :) Unfortunately I don't have any 9.3 available at this point, even all my virtual machines are upgraded to either 10.0 or 10.1.. And frankly, I don't remember exactly how it was done in 9.3.. Maybe somebody else can shed some light on it if you don't find anything useful in the docs files. -- Anders Norrbring Norrbring Consulting