In Re:
Kernel panic at boot after glibc update
Ok, i actually already fixed this, but wanted to offer some advice for those of you who were not able to figure it out.
The problem is, after a bad update of glib, i couldn't even boot my Fedora Install, due to
this bug. At boot, i was getting something like:
Code:
init[1] segfault at address ... ip ... sp ... ld-2.12.90 ...
Switching kernels made no difference. I used the live CD, and tried to follow some of the instructions that i got from the site linked to above. I
downloaded the packages linked to in comment #22. Then I tried the example used in comment #21, using local install. I couldn't get it to work (probably because i'm a noob).
How i finally got it working from the LIVE CD was as follows:
1)
download ONLY the glibc and glib-common for your architecture (i386 or x86_64) to your live desktop (or a usb drive)
2) don't use yum, but rather, use rpm, and use it in the following way:
Code:
rpm -ivh --force --root /path/to/REAL/installation's/filesystem /path/to/downloaded/glibc /path/to/downloaded/glib-common
an EXAMPLE of this command would be:
Code:
rpm -ivh --force --root /media/_Fedora_14_x86_64 /media/16_GB_Drive/glibc-2.12.90-14.x86_64.rpm /media/16_GB_Drive/glib-common-2.12.90-14.x86_64.rpm
You'll see a bunch of warning messages, but you'll be left with a bootable system again

.
I hope this helps someone, because it sucks to have to reinstall!