This post is more for myself (as a reminder) than for others \ud83d\ude42<\/p>\n
I had made a debian 4 image in vmware. I copied the base install and zipped it, when I unpacked it today and ran it, it came to ask me if I wanted to recreate some stuff. I clicked on yes (as I always did) when the Linux came up my network wasn’t working. I checked and my eth0 wasn’t available anymore, so I checked ifconfig and I found a eth1 instead. I could have replaced my eth0 with eth1 in the interfaces file but I wanted to check out why this was.<\/p>\n
It seems when you click on the Yes button, you get a new MAC address. What offcourse is logical as you don’t want the same as your other VM. I found some stuff about changing the settings in your vmx file, but found changing the udev rule easer. So I went into \/etc\/udev\/rules.d do a grep eth0 * and you find your old eth0, with the ifconfig find out the new mac address and change it in the rule. Afterwards you do a udevtrigger and off you go.<\/p>\n
You have to admit that Linux is just cool \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
This post is more for myself (as a reminder) than for others \ud83d\ude42 I had made a debian 4 image in vmware. I copied the base install and zipped it, when I unpacked it today and ran it, it came to ask me if I wanted to recreate some stuff. I clicked on yes (as … <\/p>\n