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!
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.
If you run into dependency issues they will either be in the above link or official Redhat 9 repository(ie your RH9 CDs)
You should either learn how to compile your own RPMs or switch to source tarball installation for major packages if you wish to maintain your Redhat 9 installation.
I sort of do both actually. It's an RPM install at the moment, but I'm not sure how installing a tarball over it will go.
For instance if you have say apache 2.0.49 installed, and then install the apache 2.0.50 tarball, does that overwrite the rpm install (i.e. rpm -q httpd fails or says 2.0.50)?
I also have concerns about it overwriting config files from tarball..
No, source tarball installations won't affect RPMs, RPM keeps its own database for all packages that is installed, dependencies etc.
In most cases source tarballs has default prefix in /usr/local, that's a different from the RPM install which is usually customized(genereally speaking using /usr as prefix but with some twist), so basically you have 2 copies installed, one in /usr/local which is installed from tarball, and another one somewhere else installed from RPM, and yes it may cause conflicts.
My suggestion is either go fully with RPM, compile them yourself if you can't find it on the net(this is recommended), or uninstall the RPMs and go for source tarball only. Actually you don't have to uninstall these RPMs before installing from source, but keep in mind that by default source tarballs install to a different location and they won't satisfy RPM dependencies.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.