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.
Even when I open a shell and login as root I'm not able to find the apache directory anywhere. The doumentation suggests that its /usr/local/apache. The only files that I can find are:
in the /usr/sbin directory...
1) Why is it that when I'm doing turoials ex. An Apache tutorial they are having me look in directories that don't exist. Like the one I'm doing now says as an example:
>The Apache distribution does come with another method of starting, stopping, and restarting Apache. The script is called apachectl. In the Apache src directory (apache_1.3.9/src), type make at the prompt. You will see a few more files compiled. After make is done, go to the support directory (apache_1.3.9/src/support), where you will find a bunch of new files created. Among them, you'll find a few helper scripts, including apachectl, htpasswd (used to make Apache passwords for protected directories), and rotatelogs (its use is explained later). There are a few other files, but these are the most important.
Make a copy of these three files to your Apache binary directory. If you did not change the default settings, this would be located at /usr/local/apache/bin/.
To start the server, use
There is also
I thought that all linux/unix file/directory structures were uniform? Is this a Linux Mandrake thing? This really through me way off. And this isn't the first time that I've tried to follow a doc and get totally lost. This is like assumed information which is what makes learning linux/unix very tricky. People always assume that you know so much. Atleast thats what it seems like.
2) When I use the find / -name www (logged in as non root) I get a huge list of files/paths with (permission denied)
So I su and issue the same command:
[root@localhost /]# find / -name www
find: /mnt/floppy: Input/output error
find: /mnt/cdrom: Input/output error
I did a "man find" but had a hard time deciphering the options I used. "/" tells find to start looking in the / directory? "-name" tells find to look for the Directory name "www" in the / directory?
What if I wanted to find a specific file not a directory but didn't know where this file was and wasn't sure of the correct spelling?
Thanks again. You guys have been a huge help. Much appreaciated.
This is very good to know. Is there a same command for tar files that lets you see the paths like when you do a "./configure" "make", "make install"?
I was just about to uninstall this and install from the source instead of the rpm. The only reason that I planned on doing that is because every Apache tutorial out there seem to all have the same directions and path conventions.
I.E. path conventions used in the all the tutorials I've been at use the path conventions of:
/usr/local/apache/bin (start and stop commands within here)
and numerous other examples that I'm not able to follow.
When installing from the source will this put things in directory paths listed in the tutorials? Did RPM do things differently?