> It is *highly* recommended that you change the kernel identifier at > least slightly, so that you can install '2.6.20-1.local' without > overlaying > the vendor-supplied 2.6.20-1 kernel. Among other things, this lets you > boot back to the equivalent code level in the vendor kernel, > so you can figure > out if it's your .config file that's broken, or if you hit a bug > upggrading from 2.6.19-10 to 2.6.20-1. I agree. I think your advice is *highly* recommended. I had this problem once after forcing an upgrade, which removed the working kernel. I just booted the kernel and stuff, from another partition. John. -- johnrobertbanks@xxxxxxxxxxx -- http://www.fastmail.fm - The way an email service should be - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
