View Single Post
Old 06-06-2014, 01:29 AM   #8
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by kindlecrasher View Post
Ooooooo...

So is there a chance I'll be able to boot into a minimum configuration and just delete the contents of the offending directory?

I think I have the PUTTY part down but I'm kind of at a loss for how to interrupt the boot loop and getting into a recovery console.

Any tip on where I can find that kind of info around here? Or I guess even at a Linux site or something?

Thanks.
It is printed on the serial port as the system boots - -

The first message is from u-boot, which gives you the chance to interrupt the process before it starts the kernel.

The second message is from the kernel, which gives you the chance to interrupt the process before it switches from the initramfs to the installed file system.

^^^ This will be the one you want. Then you can mount and diddle with the "main" partition as you wish. (Note: It can't get much worse than it is now. )

Last edited by knc1; 06-06-2014 at 09:47 AM.
knc1 is offline   Reply With Quote