There has to be something basic that I'm missing. This problem can't be as bad as I'm making it... other people do this...
I do a lot of work on virtual machine platforms. I also concentrate on configuration management. So, I'd really like to have it worked out so that I can deploy a new VM (cloned from a template, usually) without having to figure out what udev has decided to do with my network device names. "For system X, Configure eth1 thus; configure eth2 so; connect them accordingly."
Once upon a time I had it figured out how to get udev to just leave network devices alone. That pleased me deeply, but now I can't seem to find how I did that. I tried putting my devices in "90-local.rules", but that's a partial solution -- a cloned VM with new MAC's would need to update that.
Virtualbox is part of my problem here. For some reason, it isn't giving my VM the same MAC address across boot times. Each reboot looks like new virtual hardware. So I guess udev is doing as it's told, ignoring those MAC's (that aren't there anyway), but what I really want is to have ethN plugged into network N, ethQ plugged into network Q, and so on, like it was in olden times.
I've hunted around for a solution, but no luck. I must not be phrasing this the right way. For instance, I found:
http://www.linuxquestions.org/questi...rename-946670/
All the way at the bottom there's a solution to the problem, but it requires manual intervention. This shouldn't be that kind of a problem. It should Just Work. udev is a solution to a problem that I don't have.
