Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
While I had Windows 2000 I used its Personal Web Server for testing web pages. I now switched to Linux (Fedora Core 4), but I have no clue how to set up something similar to PWS. What's the easiest way?
I have to disagree with you on Apache. The package that comes with fedora will probably work very well out of the box and the documentation available on the Apache Site is quite good. This will work for all of your basic straight html hosting, and if you want to get into something more dynamic then you really should work with whatever platform your production server is on.
Fedora folks stop me if I'm wrong but you should just do
Originally posted by jer2eydevil88 Apache is the industry standard but it is no small deal to get it configured and working unless you have tons of time to dedicate to it then I suggest you try this out of the box solution.
Apache is quite simple to setup and there are numerous tutorials on the web. Its even simpler on distros that provide prebuilt packages, all you have to do is install the apache packages and make sure that httpd is enabled at startup or manually start it when needed.
Originally posted by uopjohnson I have to disagree with you on Apache. The package that comes with fedora will probably work very well out of the box and the documentation available on the Apache Site is quite good.
I'll second that. Apache is amazingly easy to configure, and tuning it is far easier than tuning IIS.
With IIS you have to deal with the metabase and the utilities to access it are the equivalent of BASIC's PEEK and POKE commands, whereas Apache's .conf files are human-readable at a glance. Some claim Apache configuration is voodoo but that's hardly the case, until you get down to problems like URL Rewriting. But, even when it comes to the more complex stuff, you'll appreciate that in Apache it can all be done in a config or .htaccess file whereas on IIS accomplishing the same would require coding an ISAPI plugin.
Thanks guys. I followed these instructions on installing Apache, and it works great. I have one more question, though. Suppose I want to have multiple sites to work on. How can I easily switch between them?
Thanks a lot guys, but I have just one more tiny problem. One of my web sites uses SSI in a way that the index page includes a htm file, which includes a shtml file. Like this:
The index page has <!--#include virtual="/include/footer.htm"-->, while footer.htm has <!--#include virtual="/inserts/disclaimer.shtml"-->. So basically, the index page calls footer.htm, which calls disclaimer.shtml, which has the final code. (Don't ask me why this was made like this, I'm just maintaining the site.) This will not work on my Apache. Do you have any idea how to fix it?
Hmm, where exactly do I find this setting? I've been editing httpd.conf so far, and I can't find it there. By the way, SSI does work, though partially. It doesn't work if a shtml page calls a htm page which calls a shtml file that has the code (that needs to be included in the first page).