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.
Go into /etc/rc.d and read all of the rc.* script files. They are pretty self explanatory. The most importants I think are rc.inet1, rc.modules for example. Also in the /etc/ check inetd.conf, services and identd.conf for example. Just keep on reading and use google.com/linux a lot.
slackware.org is currently a CNAME to slackware.com, and has no direct affiliation with The Slackware Linux Project. Please do not make references to slackware.org, as this may not always point to the desired location. Some cyber-squatters took it before Pat and Co. could, and refuse to relenish it, even though they forward it all to slackware.com.
Originally noted by ZoneEdit FAQ # What is a "CNAME" record?
"CNAME" records, short for "Canonical Name", create an alias from a domain name to another. You could create an alias from "yahoo.mydomain.com" to "www.yahoo.com", and every reference to "yahoo.mydomain.com" would go to the other location, regardless how yahoo changed their IP addresses! Be careful, however; CNAMEs won't work everywhere. If you create an MX record, and the name used for the mail server was defined using a CNAME, you might lose e-mail!