SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had my modem working and I could browse the Internet perfectly but I changed the NetConfig and everything went wrong. When Slackware boots up, I have to wait like five minutes because of some Mail Daemon and also I am no longer root@darkstar, I am root@127. Why? How do I set up my network if I have a modem. What do I need to set it up?
If it ain't broke, don't fix it. If you're looking to fix your hostname (darkstar/127/whatever you want), you can change it in netconfig, with the "hostname" command, or by editing /etc/hosts and /etc/HOSTNAME (caps on purpose)
The "127" probably is coming from 127.0.0.1, your loopback IP address. How that ended up in your /etc/HOSTNAME I don't know. You can out and out delete /etc/HOSTNAME and next time you boot you will be darkstar again, if you like, with a new /etc/HOSTNAME created for you. There's a lazy fix for you not the best fix though because if there is a conflict with /etc/hosts, there might be some whinging from some scripts complaining "hostname cannot be found".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
not the best fix though because if there is a conflict with /etc/hosts, there might be some whinging from some scripts complaining "hostname cannot be found". 
