Discussion:
[SLE] urgent help! I made a big mistake!
sdcoyote
2003-06-07 00:30:21 UTC
Permalink
upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an
rpm I found on rpmseek.com
Now I have a bunch of broken dependencies! how can I reinstall the original
glibc?
I have tried rpm -Uvh --oldpackage with no success! is there a way to do it
from source with make?
Regards,
paul
sdcoyote
2003-06-07 03:48:51 UTC
Permalink
This is a shot in the dark... but can someone please zip/tar the following
files from suse 8.1 and send them to me... these are the files I am now
missing since the disaster...
-p

/lib/ld-2.2.5.so
/lib/libdb.so.3
/lib/libnss_dns6.so.2
/usr/bin/db2_archive
/usr/bin/db2_checkpoint
/usr/bin/db2_deadlock
/usr/bin/db2_dump
/usr/bin/db2_dump185
/usr/bin/db2_load
/usr/bin/db2_printlog
/usr/bin/db2_recover
/usr/bin/db2_stat

please please please... will only take you a second........


----- Original Message -----
From: "sdcoyote" <***@hotmail.com>
To: <suse-linux-***@suse.com>
Sent: Friday, June 06, 2003 5:30 PM
Subject: [SLE] urgent help! I made a big mistake!


upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an
rpm I found on rpmseek.com
Now I have a bunch of broken dependencies! how can I reinstall the original
glibc?
I have tried rpm -Uvh --oldpackage with no success! is there a way to do it
from source with make?
Regards,
paul
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Anders Johansson
2003-06-07 04:04:40 UTC
Permalink
Post by sdcoyote
upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an
rpm I found on rpmseek.com
Now I have a bunch of broken dependencies! how can I reinstall the original
glibc?
I have tried rpm -Uvh --oldpackage with no success! is there a way to do
it from source with make?
Regards,
paul
rpm2cpio oldglibc.rpm > glibc.cpio
cd /
cpio -i < /path/to/glibc.cpio
ldconfig
rpm -Uvh --oldpackage /path/to/oldglibc.rpm

I had a similar situation when I upgraded from 8.1 to 8.2. The above procedure
(or a similar one) rescued me
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
sdcoyote
2003-06-07 04:16:01 UTC
Permalink
Hi Anders,
I am a little confused about that procedure... can you explain it a little
more... glibc.cpio ... what is that?
thank you...
-Paul
----- Original Message -----
From: "Anders Johansson" <***@rydsbo.net>
To: <suse-linux-***@suse.com>
Sent: Friday, June 06, 2003 9:04 PM
Subject: Re: [SLE] urgent help! I made a big mistake!
Post by Anders Johansson
Post by sdcoyote
upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an
rpm I found on rpmseek.com
Now I have a bunch of broken dependencies! how can I reinstall the original
glibc?
I have tried rpm -Uvh --oldpackage with no success! is there a way to do
it from source with make?
Regards,
paul
rpm2cpio oldglibc.rpm > glibc.cpio
cd /
cpio -i < /path/to/glibc.cpio
ldconfig
rpm -Uvh --oldpackage /path/to/oldglibc.rpm
I had a similar situation when I upgraded from 8.1 to 8.2. The above procedure
(or a similar one) rescued me
--
Check the headers for your unsubscription address
Also check the archives at http://lists.suse.com
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Anders Johansson
2003-06-07 04:20:58 UTC
Permalink
Post by sdcoyote
Hi Anders,
I am a little confused about that procedure... can you explain it a little
more... glibc.cpio ... what is that?
thank you...
cpio is a package format much like tar, where all the files are basically
streamed together in one big file. It is the internal package format used in
rpm files. With the command rpm2cpio you can extract the cpio contents from
an rpm package

rpm2cpio oldglibc.rpm > glibc.cpio

will do that, and put the cpio archive in a file called glibc.cpio

cd /

to go to the root of the file system

cpio -i < /path/to/where/you/created/glibc.cpio

will extract the contents of glibc to your file system, so you get the old
glibc back

rpm -Uvh /path/to/oldglibc.rpm

won't do much with your file system, but you'll get a nice and tidy rpm
database, so the rpm dependencies aren't broken.

It was my experience when I upgraded from 8.1 to 8.2 that rpm from 8.1 wasn't
compatible with glibc 2.3, but both rpm2cpio and cpio were, so the above
procedure should work to get you back to a working system

Next time take more care before trying to upgrade the glibc. It is probably
the most difficult thing to get right of all the things you can do with a
linux system. A kernel upgrade is a piece of cake by comparison
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
sdcoyote
2003-06-07 04:29:26 UTC
Permalink
This is the error I am getting...
cpio -i < /popper_temp/glibc.cpio
cpio: lib/ld-linux.so.2 not created: newer or same age version exists
7452 blocks


----- Original Message -----
From: "Anders Johansson" <***@rydsbo.net>
To: <suse-linux-***@suse.com>
Sent: Friday, June 06, 2003 9:20 PM
Subject: Re: [SLE] urgent help! I made a big mistake!
Post by Anders Johansson
Post by sdcoyote
Hi Anders,
I am a little confused about that procedure... can you explain it a little
more... glibc.cpio ... what is that?
thank you...
cpio is a package format much like tar, where all the files are basically
streamed together in one big file. It is the internal package format used in
rpm files. With the command rpm2cpio you can extract the cpio contents from
an rpm package
rpm2cpio oldglibc.rpm > glibc.cpio
will do that, and put the cpio archive in a file called glibc.cpio
cd /
to go to the root of the file system
cpio -i < /path/to/where/you/created/glibc.cpio
will extract the contents of glibc to your file system, so you get the old
glibc back
rpm -Uvh /path/to/oldglibc.rpm
won't do much with your file system, but you'll get a nice and tidy rpm
database, so the rpm dependencies aren't broken.
It was my experience when I upgraded from 8.1 to 8.2 that rpm from 8.1 wasn't
compatible with glibc 2.3, but both rpm2cpio and cpio were, so the above
procedure should work to get you back to a working system
Next time take more care before trying to upgrade the glibc. It is probably
the most difficult thing to get right of all the things you can do with a
linux system. A kernel upgrade is a piece of cake by comparison
--
Check the headers for your unsubscription address
Also check the archives at http://lists.suse.com
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Anders Johansson
2003-06-07 04:31:31 UTC
Permalink
Post by sdcoyote
This is the error I am getting...
cpio -i < /popper_temp/glibc.cpio
cpio: lib/ld-linux.so.2 not created: newer or same age version exists
7452 blocks
ok, make it

cpio -iud < /popper_temp/glibc.cpio
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
G***@netscape.net
2003-06-08 00:10:52 UTC
Permalink
Post by Anders Johansson
Post by sdcoyote
Hi Anders,
I am a little confused about that procedure... can you explain it a little more... glibc.cpio ... what is that?
thank you...
-----snip---
Post by Anders Johansson
Next time take more care before trying to upgrade the glibc.
It is probably the most difficult thing to get right
of all the things you can do with a linux system.
A kernel upgrade is a piece of cake by comparison.
My System Admin said the same thing after I broke my 8.0 system
installing the glibc-2.2.5-177 patch from SuSE via YOU on my 8.0 box.

The machine hung -- and he had to take it down to "Single User"
and then force the "old" glibc-2.2.5-158 rpm...

After the machine was stable again, I down loaded the new
security rpm (not the patch) and installed it (again in single user mode)

Reason: so many things are dynamically linked to glibc---



__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge. Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-***@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-***@suse.com
Continue reading on narkive:
Loading...