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.
During Slackware 13.1 setup, I chose the hostname stella-sl2.
This hostname is also the one that the system is displaying before I configured network access.
After configuring wired network access to my Apple Time Capsule, my hostname suddenly changed to INTERFACE='eth0'.
As a result I'm noticing some very strange things, like the login prompt which has become "INTERFACE='eth0' login: ".
After configuring wireless network access to the Time Capsule, the hostname changed to "INTERFACE='wlan0'". Note that, during boot, wlan0 is brought up AFTER eth0.
Also strange is this:
bash-4.1$ cat /etc/HOSTNAME
Until now, it was only a minor annoyance, it didn't prevent anything from happening, internet connection was not affected. But now I'm configuring sendmail which needs to talk to a relay SMTP server, and sendmail "HELO"'s itself using the bogus hostname:
Guess who just ran across this same problem today? :-)
Do you have avahi installed? If so, have a look at /etc/avahi/avahi-dnsconfd.action and its assumptions about /sbin/netconfig. Let me know if you can't figure out the appropriate fix :-)