On 11/26/2011 09:10 PM, Sam Varshavchik wrote:
Furthermore, if you have a corrupted libcrypt.so.1, it wouldn't matter which kernel you're booting. You wouldn't be able to boot anything. No matter which kernel you boot, you're running the same userspace, and the same set of userspace libraries. If a fundamental, key rpm like glibc is bad, you're bricked, until you fix it in rescue mode.
First, glibc was one of the things brought it. Second, I don't encrypt anything on this computer. I'll try letting it fsck itself and see what happens.