SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have made a fresh (slim) installation of Slackware 12.0 with VMware on my Windows XP notebook. I use only one network interface card on my VMware host (eth0). Everything works fine as expected, but I have a problem when I create a VMware clone from my VMware image.
When I boot the cloned image I have lost the eth0 interface. Restarting with "rc.inet1 start" results in "SIOCADDRT: no such process".
ifconfig -a shows the eth0 interface but ifconfig does not because eth0 it is not active.
I have seen another thread on this issue (why does eth0 disappear, by nyloc) but could not find any solution. Are there any news or ideas?
I now compared the log-files (/var/log/dmesg and /var/log/messages) of both boot processes (original host and cloned host). The only difference is at starting the interfaces in /var/log/messages.
In the original host /var/log/messages I find the two lines:
- sip logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.0.5 broadcast 192.168.0.255 netmask 255.255.255.0
- sip kernel: eth0: link up
In the cloned hosts /var/log/messages the above two lines are missing, and there is a line instead
- sip logger: SIOCADDRT: No such process
Why does this process not start from a cloned image?
Does anyone have an idea? Or how to repair the situation on the cloned host?
Any help highly appreciated!
Last edited by efranz; 08-22-2007 at 03:36 PM.
Reason: Further analysis of boot process
I removed the /etc/udev/rules.d/70_persistent-net.rules, but it is being created every time I start the VM, and the eth0 is still not visible in ifconfig.
I'm using slackware 12.1 on vmware.
If that is after the vm boot then the eth0 device is known to the kernel but does not have a IP assigned. What does your '/etc/rc.d/rc.inet1.conf show for the eth0 device. You did run 'netconfig' or physically setup the eth0 in the 'etc/rc.d/rc.inet1.conf' file?