On Fri, Feb 15, 2013 at 3:52 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > >>>> I don't understand how you create that udev entry before you need it >>> >>> easy if you know the MAC address >> >> Do you mean you make the change in a virtual system image before >> copying/changing the virtual MACs? Or in a script that runs during >> boot up before the network comes up? > > before changing the MAC Most of our machines are physical and the issue happens when I swap disks to a new chassis or clone images. The same solution 'could' work, but I generally don't know ahead of time where the image is going. >>>> Or why one udev-assigned name is different from any other name once >>>> it is in place in that file >>> >>> you know what race-condition means? >>> https://bugzilla.redhat.com/show_bug.cgi?id=782145 >> >> I suppose that's possible, but doesn't have much to do with the issue >> of making the ifcfg-* files match the MAC address. > > WTF - this issue does not exist if you are not so stupid > and place the MAC address additionally to the udev-rule > in the ifcfg-* No, the link you posted has to do with a race between the kernel itself and udev. Nothing to do with what happens at ifup time. Things would already be broken by then, though. I do see how not using the same names the kernel would auto-assign would avoid the race problem, but I'm not sure it happens in CentOS. If you use fedora, you deserve the extra bugs. -- Les Mikesell lesmikesell at gmail.com