LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   almost painless machine upgrade (https://www.linuxquestions.org/questions/slackware-14/almost-painless-machine-upgrade-4175466145/)

unclejed613 06-15-2013 12:04 PM

almost painless machine upgrade
 
had my machine crash this week, badcap disease in the power supply, so i decided it was time to get a "new" machine... actually it's a refurb. all i did was take my disk out of the dead machine and put it in the new one (along with the video card). half expected to have to reinstall slack or do some major tweaking. as it turned out it was rather painless, it just worked out of the starting gate. except for one thing. i had to look at /var/log/messages to find it.... "renamed eth0 to eth1". after telling wicd that the wired connection was on eth1, i had network again. maybe somebody could explain why eth0 is now eth1....

allend 06-15-2013 12:14 PM

Delete /etc/udev/rules.d/70-persistent-net.rules to remove the dead machine network device entry and reboot.

Timothy Miller 06-15-2013 12:14 PM

I would assume because you have a different NIC, and so it recognizes it as a different device. The system keeps track of all your network devices it sees, and so still remembers eth0 as your original NIC. I'm too lazy to go grab the machine I have Slackware on, and have never had this trouble so have never looked, but in MANY modern distros, if you wanted to rename your NIC to eth0 you'd edit udev policies. /etc/udev/rules.d/70-persistent-net-rules or the like, rename/remove eth0 and then change eth1 to eth0 (or deleting both to have it recreate). After rebooting, your NIC will be eth0 again.

unclejed613 06-15-2013 12:33 PM

tnx, everything seems to work ok, so i'll leave it as it is (if it works, don't fix it).... i was just wondering why it did that...


All times are GMT -5. The time now is 06:04 PM.