"Keith & Cecile Schooley" wrote: >In the process of compiling a new kernel, I renamed my /lib/modules/2.2.17 >file. I won't take you along the convoluted process that made me think that >that was a good idea. Anyway ... > >I can't boot up. I keep getting an endless series of messages that >/lib/modules/2.2.17 can't be accessed because it isn't there. Is there >anything analogous to Windows' "safe mode" that could get me into the system >just enough to get to /lib/modules/2.2.17-old and change it back? > >Boot floppy doesn't work; it just gets me to the same point. Any >suggestions before I decide to re-install?
boot: linux init=/bin/bash This should stop before anything that needs modules is loaded. Don't forget to sync your disk before rebooting. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C ======================================== "The LORD is my light and my salvation; whom shall I fear? the LORD is the strength of my life; of whom shall I be afraid?" Psalms 27:1
