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
The specific message is that /sbin/sulogin failed because it coulden't
find libcrypt.so.1.
I touched /forcefsck and rebooted into the F16 kernel and it hung.
Tried again with the F14 and it either ignored the /forcefsck or it'd
been nuked by the failed boot. Will try again.