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.
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.
Just finished up the apache section on the web site. You can check it out at http://shilo.is-a-geek.com/slack/apache19.html . Let me know what you think. As always, criticisms, comments, and tips always welcome.
Nice page - as always I have some questions, though...
You say that the served files are in /var/www/htdocs. Are you sure about this? Firstly, when I had a web server running (for a very very short time, in which I didn't really had time to get things in order) I put my stuff in /var/www. That might be completely wrong - what do I know - but also, secondly, the directory seems a bit strange: why put the served pages in a dir called htdocs?
(That comment is related to my wondering why you put the guide under shilo.is-a-geek.com/slack/ when you haven't put anything at the "root", shilo.is-a-geek.com/ . But I guess you have your reasons, it's just me thinking too much )
The other comment is just a thought from where the [warn] module mod_php4.c is already added, skipping is coming from. (1) Is the AddModule mod_php4.c line necessary? Or (2) are that line and the LoadModule php4_module libexec/apache/libphp4.so line in the correct order?
Distribution: Mainly Slackware, but test run various different distros.
Posts: 77
Rep:
actually it all depends on how you have your apache configured.. htdocs is the default site root, but you can change that to anything below the www folder. i dont think you can go outside of that folder without creating symlinks to the directory. So yes Bebo, it is possible that your root was /www. apache is a LOT more forgiving when it comes to customizing than IIS.
nice writeup shilo.. great detail on the httpd.conf (which can be one of the first places where things start to go down hill if you set it up wrong!).
Like Systematic said, /var/www/htdocs is the default root. I believe it stands for "HyperText Documents". Also in the /var/www directory is the cgi-bin directory and the icons directory. I believe that these directories exist to save some confusion which might be caused by placing everything in the /var/www directory. I try to keep everything as stock as possible. Makes trouble shooting a lot easier.
As for the directory structure on my site, I have a few projects that I'm working on for my site. I haven't had a chance to make something for the main site yet. In retrospect, the slackware section is the only popular section and I probably should have made it the main site. Oh well, live and learn.
Thanks for the tip on the modules, I'll check it out tonight. If it works, I'll edit the site.
Distribution: Ubuntu Server, Slackware, Red Hat 6.1
Posts: 241
Rep:
I .. third that idea.
This thread is worthy of a sticky. If not this thread, then a reorganized new thread that pieces the different parts of Shilo's guide one after the other.
Thanks for all of the kind words and the bumps, everyone.
Bebo-
Thanks for the tip on the php module I commented out the AddModule Line and everything seems to be perfect.
If anyone was trying my site yesterday or early today, sorry. I upgraded the firmware on my router and managed to make a mess of things. Everything seems to be running fine, now.
Anyone have any pointers on how you can change the default directory of Apache? For my webserver, I would like to move the default Apache htdocs to /home/htdocs. I have partitioned a rather large /home partition for this purpose. I currently host about 25 - 30 websites so I would like subdirectories for each site under /home/htdocs or /home/companynameweb.
I was reading the website, and in the 'Going Graphical' section you give a bunch of links to images for the lilo prompt, thank you for puting mine in there, but I notice that the link is not working, you gave this link: http://www.geocities.com/mctarnet/images/lilo2.bmp which gives the user and unavailable page. I'll suggest to change it to: http://www.geocities.com/mctarnet/images/ from there the image can be donwloaded.
Great work with the website and everything. I have read from many post that it will be nice to have a printable version in PDF, if you don't mine I could do that, unless another person have already undertaking the job.
Once again grate job with the site.
wow! great guide and great discussion! shilo you're the man! i reinstalled last night, and as soon as i can figure out why my keyboard and mouse won't work in X, I'm going to get started on cleaning things up and tweaking. i'm really looking forward to it!
I just though of an alternate solution to resetting your default root directory. Make a symlink between /home and /var/www. That way, you don't have to mess with configuration files. Probably not the best way to go about it, but I beleive it will work. Also, I believe that wit hthe configuration that I have posted on the site, you can place a file named public_html in a users home folder and that folder can be accessed with http://name_of_your_website/~name_of_the_user . That is, if your websites were individual user websites.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.