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.
Which is better for all kinds of use: IIS or Apache? And please be specific. Which can do more, which is securer, which will be easier to use, setup a webserver on, and other various things. A comparison chart would be nice. Thanks in advance.
I thought this thread was a joke too when I read it.
Apache is probably harder to setup, but just because you actually have to edit the apache.conf file (gasp) instead of the Windoze check-box setup.
Once apache is up and running, it is a snap to maintain. However for IIS, your more likely to end up do 5-10 at Chino because some h4ck0r used your box to store warez. I would seriously think about using apache before you connect anything running IIS to the internet.
Editing a file is probably alot easier than rebuilding Windoze everytime you get hacked.
statistics show that 42% of statistics are made up on the spot, but I believe they say that 64% of webservers on the net are running Apache. The strange thing is that 86% of webserver hacks are on IIS. 72% of those hacks are by 1-legged bi-polar teenage alcoholics. If you don't believe that, check with the experts, 97% of them will agree with 29% of the facts.
If you intend to put up an application server using some sort of Java Beans, then I would suggest Apache as well. There are modules already there for just about any J2EE app server you could think of running.
If you intend to put up asp pages or use .Net, then I suggest you have your head examined, then change your mind and put up Apache using one of the previous mentioned solutions.
In terms of security, IIS has way to many problems, Apache is about as close to rock solid as you can get. When a major heavyweight like the Gartner group recommends that businesses make the switch from IIS to Apache... That says something. Taking a major corporations' Web-servers and switching the entire platform on which they operate is no easy undertaking. $$$CHI-CHING$$$