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 was looking to see what daemons started at the gui runlevel, usually runlevel 5. So, I looked in the /etc directory and there was no rc5.d directory in there. all I could find was the rc.d directory which had the rc4.d config file. It stated that in was the config runlevel. I'm used to Fedora and this is quite different. Where do you select the default daemons for the run level in slack? I couldn't find anything in th /etc directory.
Yep, I wanted to see what daemons started at boot. With Fedora/Redhat you just go into the rc5.d and rename the files to have a S for start or a K for kill. It confused me when those directories didn't exist. I'll check out the intid.conf file after work.
To see a overview about the /etc/rc.d directory go here: http://www.slackware.com/book/index....SYSTEMOVERVIEW
and scroll to The /etc/rc.d Directory
Basically, you don't have runlevel directories, but file, and each service (if started stand-alone, you could use /etc/inetd.conf as stated, but this works only for network apps) is given a rc file. Like Apache has /etc/rc.d/rc.httpd, SSHd has /etc/rc.d/rc.sshd. To know if it will be run as startup, you just have to see if the file is executable or not (the permissions).
pkgtool as __J said, has a front-end to this rc files, it will basically make them executable or not depending on what you choose. To change the permissions manually, just chmod -x /etc/rc.d/rc.httpd for example.
As for what's running, the same services as runlevel 3. Everything that's executable in /etc/rc.d/
In addition, it runs /etc/rc.d/rc.4, which calls GDM, KDM, or XDM in that order of preference. The only difference between RL3 and RL4 in Slack is that RL4 has X running.
What I was trying to do was to mount an NFS share on to my new slack system and the mount command hung until you close the term. It is much different than my fedora system. I needed to enable the portmap file so I made it excutable. where do you find the nfsd and smbd services?