-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/04/2009 09:29 AM, Bruno Wolff III wrote: > On Sat, Apr 04, 2009 at 07:47:26 -0500, > Mike Chambers <mike@xxxxxxxxxx> wrote: >> I ran into this during the middle of devel between alpha and beta. What >> I found out, was when doing any kind of major update like above, just >> boot into run level 3 first and then run the upgrade. That way X or >> anything else doesn't try to restart or anything and interrupt the >> update and cause problems like you experienced. > > Other options for when things are really hosed are to try booting to run > level 1 or using a rescue disk / image to boot. > For me, I had done an clean install of the Beta, it worked and then I did an upgrade via PackageKit and the machine crashed during the upgrade and then I was left with a locked down system. So I followed the normal process. I realize this is a beta, but that is a pretty serious issue. Kevin - -- Get my public GnuPG key from http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAknXfh0ACgkQ6w2kMH0L1dFlRwCePZtyFrhOcPLxojEosYuJgXlt IJEAn2DRKVQlo7yPozt8fRJ8+DRHiirm =BvMb -----END PGP SIGNATURE----- -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
