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.
I have a few questions about web hosting. So lets begin:
1. I heard Apache is used for web hosting. How would I go about using Apache?
2. Would Slackware Linux be good for hosting email accounts/web sites if I used apache?
3. Would I still be able to run Slackware as I usually would without any anoyying things that wouldn't happen if it where a regular desktop?
4. How much would I cost to host web/email using Apache?
I will probaly ask more and more questions as time goes by.
Are you hosting sites for others, or are you researching for a website that will host your own site. To me, the answers to those questions depend on which you are doing.
[ If you're hosting sites for other people ]
1. Install and configure apache for virtual sites.
2. Slackware would work as would any other linux distro. Some people look for a specific distro when they are hunting for a host.
3. A server should run only as a server since people are paying for performance and uptime.
4. Depending on the speed, you could charge anywhere from $0 to $40 a month.
[ If you're looking for a site to host you website ]
1. They'll already have either apache or IIS installed
2. They may run slackware, or they might run other distros
3. You can use a slackware desktop to access most webhosting sites to administer your own website.
4. Depending on the speed, they might charge anywhere from $10 to $100 a month.
Last edited by musicman_ace; 12-17-2006 at 06:36 PM.
If you don't have a static IP address (or at least one that doesn't change very much) you'll probably want to use something like dyndns.org or no-ip.com. As for your questions:
1) Install the software, edit the httpd.conf, start it up, and start putting files in the document root.
2) Sure -- I run my internal Web server on my Slack desktop. Slackware has packages for Apache and most commonly used add-ons (for a more custom setup, you may need to compile some stuff from source).
3) Since my Web server is internal (only for my home LAN of ~ 10 machines) traffic is extremely light and security concerns are minor (all access is blocked by my firewall). If you intend to serve up sites to the world at large I would highly recommend using a dedicated machine both for performance and security reasons. Ideally, you would have the server segregated onto a DMZ on your network or some such setup.
4) Apache is only a Web server. If you want to host mail you'll need a SMTP server and (probably) a POP3 or IMAP server.
As twilli227 said, you should check and make sure your ISP's terms of service allow for hosting servers. This is particularly a problem with mail servers since many ISPs block them due to spam concerns. Even if you can receive mail, many sites block mail originating from home IP addresses, again, due to spam concerns. It's generally best to relay outgoing mail through your ISP's mail server (via the SMART_HOST directive in sendmail or its equivalent in other mail transport software).
Plus any expenses for domains etc, extra bandwidth (maybe another line to handle it?)
I don't really understand the point of your question, you need to sit down and work out the figures, the time, and any extras, somebody here cannot quantify it for you.
The software (apache et all) itself is free btw.
Seems your other questions weren't answered:
1) Depending on the distro, it'll probably have a wiki or something (i'm spoilt by arch) on how to set it up. If not, LQ will have something, or their site http://www.apache.org/
2) The distro is irrelevant really, in terms of running apache as they all can, i'd base it on other factors, such as how well you can configure/support it, which services you require, etc etc. But yes, slackware is fine for apache.
3) Running a webserver is just running another service, accepting some extra traffic, it doesn't make it 'server only' or anything, although, depending on your traffic you may not want the machine doing anything extra.