Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Why do you have Apache listening on port 8080? Don't give up hope. If you can not access http://localhost or http://your.ip.address.here then apache is not running. Either there is something misconfigured in your httpd.conf file or you haven't started apache.
Does this tell you that apache stopped[OK] and started[OK]?
This is exactly what it says in the terminal:
Shutting down httpd-perl: [ OK ]
Starting httpd-perl: [ OK ]
Starting httpd: [ OK ]
**BLANK LINE** [ OK ]
**BLANK LINE** [ OK ]
[ root@whoracle root ]#
I originally thought that it should list Apache in there somewhere, but, I'm new to Linux, and wasn't sure. Any ideas?
Oh, and for the Port 8080, thats the way its setup, haven't changed a thing.
Only problem with that...I'm a total Linux n00b, and will probably screw something up I'm not even sure how to install something on Linux yet...other than by CD. What can I say. It really doesn't matter to me, if I can get my 1.3 version of Apache to work...I'm content
Hey, I'm really new too.
Been addicted to using prebuild .rpm packages so far, but now I'm starting to gunzip, ./configure, make, make install a few things like apache. Not hard, just a few commands and waiting for the compiling (not long on this beast)
Hardest bit is reading up on what non-default options you want to pass while doing this.
I have httpd-184.108.40.206.tar.Z downloaded...and have opened it with GnoZip, but have no idea what to do from there...I've read the whole installation guide on Apache.org...but it seems to be directed towards rocket-scientists
If you've extracted the .tar.gz, then navigate into the folder it created, and open a terminal (Assuming KDE and Konqueror)
The type su
Enter the root password
Then type ./configure
If you get through that without an error, type make
Again, if no problems, type make install
Should be installed now
As that was from memory, I might have forgotten something. Check the readme and install (text) files in the extracted directory.
Specifying the install directory seems to be missing from my explaination
Whoracle-the easiest thing to do at this point is to uninstall apache and then re-install it. Since you've been tinkering around in those conf files for so long you may have changed something that is hidden in the depths of your filesystem.
Also my suggestion would be to install the rpms instead of by source. A lot of people are die-hard about installing from source but I find the rpms much more noob friendly.
If you do take my suggestion this is how you locate, uninstall, and re-install apache as root from a command prompt:
1. Locate Installed Apache Packages
rpm -qa | grep apache
You should see a listing off all installed apache packages.
2. Uninstall Apache Packages
rpm -e apache*
3. Install Newly Downloaded Apache Packages
Download all the latest apache packages from wherever you can find them. To install them, change to the directory where you downloaded them and issue this command:
rpm -ivh apache*
As I said before this is only a suggestion so if you don't feel like uninstalling and re-installing thats fine. I just think it would be a little easier to configure apache now that you've finished with your trial-and-error method. When I first started using Linux I was the king of uninstall re-install because I screwed up the conf files so much.
computer or compiler?
Didn't you install the developers packages when installing Mandrake? You're kinda gunna need a few common things, like gcc as a c source compiler
Fire up rpmdrake and break out your cds.
Ok, delete that extracted directory and unpack a fresh one.
Now try the same again, but this time use ./configure >attempted_install.txt
That should be the command to dump the output into a txt file it'll create.
Then when the same error stops the process, we can look back up and see what it found when looking for an acceptable c compiler.