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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been using Apache 2.2 for a long time now. This morning I updated to Apache 2.4.3.
I have never installed a version of software that is not in the repository before on Debian. (I've custom compiled other distros, but not in Debian.) Is it normal to not be able address Apache as Apache2 in the terminal after installing a package from tar.bz2 file?
What I mean is that when I install a package from the repository simply using apt-get I can refer the the package by name. For example if I want to restart Apache I could do
/etc/init.d/apache2 restart
or if I want to find out information about the installed package I could do
dpkg -s apache2
But after installing the newer version of Apache I can't do those things by using the name 'apache2'.
I can of course still stop and start Apache by using it's exact location, but I'm just curious if it is normal to not be able to call the package by name when installing using a version not found in the repository.
I am also looking for some good Apache 2.4.3 documentation that goes over the differences in 2.2 and 2.4. There are a lot of major changes in 2.4. I've looked through apache.org but I haven't found anything that goes over the differences.
A big change I noticed that the www directory is no longer is /var/www. It is in the hdocs directory under /etc/apache2/hdocs.
Did I simply mess up my install or is this in fact the new place to keep the web documents?
If anyone knows of some good documentation that can help me transition into this newer version of Apache I would very much appreciate it.
And yes, my Apache install works. I'm just wondering if I did some things wrong or there are just a lot of changes in the software.
Thanks.
Last edited by fail-distraction; 01-20-2013 at 07:32 AM.
@kox444, yes, I could change it. I just want to be certain if there not being a www directory under var is just something new in Apache 2.4.3 not a mistake I made when installing.
Did you create a DEB package and installed that or did you just installed from source without creating a package?
I'm not sure exactly what you mean. Do you mean did I make and make install? (I do not know how to make a DEB package, unless that is what the make command does.)
I installed it like this
first I installed the apr and apr-util cd to-my-apache2.4-directory-location ./configure --prefix=/etc/apache2 make make install
OK, so you did not create a DEB package, that is the reason why you can't ask the package manager for information about the Apache package, simply because it can't know anything about a software that, from the package manager's view, simply doesn't exist.
Information how to build DEB packages can be found here: http://www.debian.org/doc/manuals/ma.../index.en.html
Just had a look at the httpd.conf for Apache 2.4.3 in Slackware, it looks like the default DocumentRoot option is /srv/httpd/htdocs.
Since Slackware aims to be close to upstream I doubt that this is a Slackware specific option, it seems to be a new default, although it may be possible that Debian patches this to be /var/www.
Just had a look at the httpd.conf for Apache 2.4.3 in Slackware, it looks like the default DocumentRoot option is /srv/httpd/htdocs.
Since Slackware aims to be close to upstream I doubt that this is a Slackware specific option, it seems to be a new default, although it may be possible that Debian patches this to be /var/www.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.