glibc recovery *success*

Subject: glibc recovery *success*
From: Rob Cermak (cermak@sfos.uaf.edu)
Date: Fri Apr 11 2003 - 11:52:27 AKDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Jim Gribbin: "not exactly linux ..."
• Previous message: Rob Cermak: "RH9/glibc: Redhat has it in bugzilla: glibc"

(1) post mortem using: linux recover

rpm --root=/mnt/sysimage -qa | grep glibc

showed that glibc-common was updated, but both
glibc packages exist in the rpm database.
  OLD: glibc-2.3.2-11.9
  NEW: glibc-2.3.2-27.9

Looks like something failed in the update process.

(2) removed glibc-2.3.2-11.9
    rpm --root=/mnt/sysimage -e glibc-2.3.2-11.9
    reinstalled glibc-2.3.2-27.9 : if you happen to have
      in on the failed system somewhere ; burn it to CD
    rpm --root=/mnt/sysimage -Uvh --replacepkgs --replacefiles glibpkg

(3) test it out
    chroot /mnt/sysimage

You will know if the system fixed if the chroot does not segfault.

(a) chroot worked
(b) rebooting: its doing fsck's on the journaled filesystems,
    seems like we are back in operation.

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.

• Next message: Jim Gribbin: "not exactly linux ..."
• Previous message: Rob Cermak: "RH9/glibc: Redhat has it in bugzilla: glibc"

This archive was generated by hypermail 2a23 : Fri Apr 11 2003 - 11:52:29 AKDT