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.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
If you are using dhcp you do not have to do anything to the resolv.conf file.
When you are running dhcpd and you are getting your ip from a dhcp server the resolv.conf is written over at reboot, lease expiration, a inetd restart, or if netconfig is ran.
If you are on a static ip and I will assume you have all ready configured /etc/rc.d/rc.inetd.conf with the static ip, netmask, dhcp name and the default gateway then you must configure the resolv.conf with your local dns server (if you are running a correctly configured bind) and/or your ISP nameservers. You may also put in other nameservers here also.
Note on bind nameserver and slack.. A low end cacheing nameserver is installed by default in slackware BUT you should edit this as required for maximum benefit. Please use the HOWTOs and the bind manual for a improperly configured bind nameserver can cause undue traffic on the internet and your local net.
nameserver 127.0.0.1 #LOCALHOST IF RUNNING A NAMESERVER
nameserver ###.###.###.### #local network nameserver ip
# From here you can add other nameservers like your ISPs
Now this is not all....
resolv.conf also depends on you having your hosts file configured it will search it first. You can add to the /etc/hosts file local machines, frequently visited networks, websites or other network places to speed getting to them. This is very handy as it allows faster access as it name to ip is done locally. The hosts file is also where you may id aliases for you machine also.
Note also that you can do this on windors also. The hosts and lmhost are located in the c:/windows/system32/drivers/etc directory. They are configured much like the unix version.