Hi Sean,
Thanks for your reply. I cannot use RPM to do the library upgrade because of
the following
reasons:
o It is very difficult to satisfy all the RPM dependencies.
o I do not have development environment on my target Linux box
(bare bone system)to
build everything from the source RPMS.
When I tried to install from the binary RPMS I got the following error
messages:
First I tried to update my RPM 4.0 to RPM 4.1 (required by glibc-2.2.93-5).
rpm -U rpm-4.1-1.06.i386.rpm
error: failed dependencies:
libelf >= 0.8.2 is needed by rpm-4.1-1.06
libbz2.so.1 is needed by rpm-4.1-1.06
libelf.so.0 is needed by rpm-4.1-1.06
rpm = 3.0.4 is needed by rpm-build-3.0.4-0.48
rpm = 3.0.4 is needed by rpm-devel-3.0.4-0.48
librpm.so.0 is needed by rpm-build-3.0.4-0.48
librpm.so.0 is needed by ucd-snmp-4.1.1-2
librpm.so.0 is needed by ucd-snmp-utils-4.1.1-2
librpmbuild.so.0 is needed by rpm-build-3.0.4-0.48
I do have libelf-0.8.2 and libbz2.so.1 on my target machine. Why does RPM
still complain about it?
When I try to do glibc upgrade, I get:
rpm -U glibc-2.2.93-5.i386.rpm
glibc-common = 2.2.93-5 is needed by glibc-2.2.93-5
glibc-devel < 2.2.3 conflicts with glibc-2.2.93-5
glibc > 2.1.3 conflicts with rpm-4.0-6x
libdb.so.2 is needed by passwd-0.64.1-1
libdb.so.2 is needed by rpm-build-3.0.4-0.48
libdb.so.2 is needed by ucd-snmp-4.1.1-2
libdb.so.2 is needed by python-1.5.2-13
libdb.so.2 is needed by ucd-snmp-utils-4.1.1-2
libdb.so.2 is needed by rpm-4.0-6x
libdb.so.2(GLIBC_2.0) is needed by python-1.5.2-13
libdb.so.2(GLIBC_2.0) is needed by rpm-4.0-6x
libdb.so.3 is needed by perl-5.00503-10
libdb.so.3 is needed by pam-0.72-6
libdb.so.3 is needed by python-1.5.2-13
libdb.so.3 is needed by sendmail-8.9.3-20
libdb.so.3(GLIBC_2.0) is needed by perl-5.00503-10
libdb.so.3(GLIBC_2.0) is needed by python-1.5.2-13
libdb.so.3(GLIBC_2.1) is needed by perl-5.00503-10
libdb.so.3(GLIBC_2.1) is needed by pam-0.72-6
libdb.so.3(GLIBC_2.1) is needed by sendmail-8.9.3-20
Thinking that upgrading glibc-common will help:
rpm -U glibc-common-2.2.93-5.i386.rpm
error: failed dependencies:
rpmlib(PartialHardlinkSets) <= 4.0.4-1 is needed by
glibc-common-2.2.93-5
glibc < 2.2.93 conflicts with glibc-common-2.2.93-5
Could you please let me know the exact order in which the RPMS have to be
updated and how to
update RPM 4.0 to RPM 4.1 ?
Is it required that I need to have glibc-devel also installed ? As I pointed
out earlier, the
target machine is built without any development tools on it.
Any help would be greatly appreciated.
Thanks & regards,
Raj Mohan
-----Original Message-----
From: Sean Estabrooks [mailto:[EMAIL PROTECTED]
Sent: Monday, August 25, 2003 6:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Help - Upgrading system libraries
On Mon, 25 Aug 2003 13:32:10 +0200
"Mohan, Raj" <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have a RedHat 6.2 installation that I would like to upgrade with the
> RedHat 8.0 system libraries (glibc etc.). I tried the following steps:
>
> o Saved the existing RedHat 6.2 /bin, /sbin. /lib to the following
> directories respectively:
> /RH62/bin,
> /RH62/sbin.
> /usr/i486-linux-libc5
>
> o Changed the symbolic links in /lib to point to /usr/i486-linux-libc5.
> o Copied over the RedHat 8.0 /bin, /sbin and /lib on to my RedHat 6.2
> machine.
> o Tested the commands from /RH62/bin. They work.
> o Created new links in /lib to point to the new RedHat 8.0 libraries.
> o Executed ldconfig.
> o Now when I try any of the commands from /bin I get the error "ILLEGAL
> INSTRUCTION".
> o I cannot recover back my system anymore.
>
> Questions:
> 1. What am I doing wrong ?
> 2. Is it possible to update system libraries this way ?
> 3. The RedHat 6.2 machine is remotely located and can only be updated
via
> a server machine due to security considerations.
>
>
> I could create a custom kernel on my RedHat 8.0 machine and install it
on
> the RedHat 6.2 machine. This works without any problem.
>
> Since I have the RedHat 8.0 kernel on my RedHat 6.2 machine now, I would
> also like to upgrade the libraries to RedHat 8.0
>
Hi Raj,
On a Redhat system, it's best to let rpm do the upgrade for you with
the -U option.
Now, no commands will work on your system because they were linked
against the old libraries and can no longer find them. You'll need to
boot from the CDROM and restore the old libraries. Actually, if you have
a working NFS or SAMBA mount you can restore your libraries that way too.
Once you've fixed your system, try upgrading with the rpm command.
Good luck,
Sean
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
