There is no reason to remove if you are replacing with a similar method. Therefore, you can upgrade .RPMs with .RPMs and you can replace source-compiled binaries with new compiled versions IN The SAME destination folders.
What gets icky, particularly on RedHat boxen is trying to replace SSH .RPMs with SSH source. If that's what you need, let me know here and I'll try to make some sense of my prior efforts.
"Surfinbox Shares" - A fundraising program that builds revenue from dialup Internet users.
2) reviewing both my /opt/7.3/patches directory and /var/logs/rpmpkgs directory:
kdessh-3.0.0-4.i386.rpm
openssh-3.1p1-6.i386.rpm
openssh-askpass-3.1p1-3.i386.rpm
openssh-askpass-gnome-3.1p1-6.i386.rpm
openssh-clients-3.1p1-6.i386.rpm
openssh-server-3.1p1-6.i386.rpm
However doing a rpm -verify openssh....
on each one reveals:
rpm ... not installed.
This leads me to believe that ssh was installed with source not with an RPM. Am I correct? How Can I verify whether installation was with RPM or source?
OK, let's take one thing at a time.
First, the listing you show indicates what has been installed on the system. Installed and running are entirely different. Your car has a spare tire, but it's not necessarily in use.
It looks to me like you did the incorrect method of adding an update of SSH .RPM packages. Thus you have two instances of the same programs, at least in the .RPM database, which is going to cause no undue confusion. You need to execute the following commands to clean things up a bit.
Next you need to get a set of the newest OpenSSH .RPMs from rpmfind.net or redhat.com or anywhere... you are behind in ssh versions.
ONCE YOU DOWNLOAD THE .RPMS use the 'rpm -Uvh XXX.rpm' construct. This upgrades the prior version of the same program through replacement!! Very important.
You should be able to check the same issues with Apache and OpenSSL, undo any duplicated installs by removing the older version of the files, and use -Uvh to fix the damage with the newest .RPMs.
If you are showing the same versions of .RPMs as are available for download, do the download anyway and use the '--force' parameter to ensure that the .RPM gets installed properly.
Surfinbox.com Business Internet Services - National Dialup, DSL, T-1 and more.
glibc 2.3 or greater is required for ssh 3.7.1 ; however glibc 2.3 is not available for rh 7.3. I guess I have to upgrade to a higher level of rh? Or can I just grab the glibc for rh9 and install on my 7.3 system?
I have to guess at this point that you're trying to install the wrong .RPMs for your version!!
Rather than take a great deal of time to fix it - which may not be possible - have you considered re-installing the system? Is this an option? You're in an ugly situation that will never get better..... Perhaps you'd like to use RH9 to install anew with?!
Surfinbox.com Business Internet Services - National Dialup, DSL, T-1 and more.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.