Thanks Artem, I've added this to F14Blocker list, as it clearly impacts
the final release criteria if all systems fail to boot.
This updated required a few additional steps in order to rollback the
glibc update to return to a working system. ÂAs with anything, there are
many different ways to accomplish this. ÂIn case folks are interested, I
included my recovery procedure below ...
  1. Boot into a rescue system (this could be the F14 installer
   Ârescue-mode, a previously installed Fedora on another partition,
   Âor a Fedora Live image). ÂIn my case, I have an F13 partition on
   Âmy system.
  2. Identify and mount your F-14 installationrescue-mode will locate
   Âand mount the partition for you). ÂIf not ... some manual steps
   Âmay be required. ÂFor me, it involved unlocking the encrypted
   Âpartition ...
      Â* UUID=$(cryptsetup
       ÂluksUUID /dev/mapper/vg_flatline-f14_root)
      Â* cryptsetup luksOpen /dev/mapper/vg_flatline-f14_root
       Âluks-$UUID
      Â* mount /dev/mapper/luks-$UUID /tmp/f14
      Â* mount -t proc proc /tmp/f14/proc
      Â* mount -t sysfs sysfs /tmp/f14/sys
      Â* mount -t selinuxfs selinuxfs /tmp/f14/selinux
      Â* mount -o bind /dev /tmp/f14/dev
  3. Downgrade glibc* packages. ÂAgain, for my recovery procedure,
   Âthis involved ...
      Â* yum --installroot=/tmp/f14 downgrade glibc*
  4. Reboot your system into Fedora 14 ... and wait for a new and
   Âimproved glibc update to test
Thanks,
James
Sadly this isn't working for me, I get an error from yum stating that it was unable to load yummain. I have tried booting from a f14 alpha rescue disc and from a f3 rescue disk as well as working from a f13 live image and none of the above works to downgrade glibc. Any other alternatives?
Thanks,
-Erinn
Â
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
