Originally Posted by fatalerror0x00
of the slackware setup daemons are what i need to know what ones do i need active to have all the features I'm requesting
I'm not sure if you're asking a new question or just repeating your original post.
listed the files found in the /etc/rc.d
directory that need to have execute permission turned on so they will run at boot up ( chmod +x <file> ). Slackware is configured so that if execute permission is set on the files in /etc/rc.d
directory then the services/daemons/servers found in those files are started at boot up. To stop a daemon from running at boot up just remove the execute permissions ( chmod -x <file> )
If you look at the contents of each of these rc.xxx
files you'll see daemon that will execute. You may open a man page on each one for additional information. (e.g. man httpd)
The default setup of most "servers" do a pretty good job of getting a basic server running. You'll still need to learn about, configure and set up each of these "servers" (daemons) to meet your needs. For example, knowing that your web pages go in in /var/www/htdocs by default. (Note that when the Apache web server comes up (httpd) it provides you with documentation on its web page (http://localhost
Rather than asking further wide ranging questions why not try getting each of these daemons working one-by-one.
Read the documentation for each daemon. If you have trouble with a particular daemon as it's implemented in Slackware and you've read the documentation on it provided by the Slackware (man pages, /usr/doc/xxx, /usr/doc/Linux-HOWTOs)
... and you've read the documentation on it provided by Slackware supporters (docs.slackware.com, alien.slackbook.org, wiki.linuxquestions.org/wiki/Slackware-Links)
... and you've searched online for the answers (Google, LQ, daemon web site)
... and you've experimented and you've run out of ideas
post your question on your specific problem
and the friendly knowledgeable members of LQ will be happy to help out.
It's also okay to ask a simple basic question to get started. For example, if you didn't know that the daemon for the web server was httpd. But just ask one question at a time.
I understand your enthusiasm for all things Slack but the learning process (and assisting process) is much more efficient by handling one simple problem/question at a time.
Just a suggestion.