View Single Post
Posts: 384 | Thanked: 90 times | Joined on Mar 2008
#295
Thanks! So you said:

Originally Posted by Benson View Post
Excellent! Rebooting now would make things quite hard to recover indeed.




Looks like you've attempted to upgrade with the SDK repo enabled, causing conflicts with busybox.

I'm not familiar enough with Debian packaging to be sure what you should do from here, but I think none of that would work anymore. As I understand it, you are currently stuck with no tar, and probably no shell, so installing packages may not work...

First order of business, then, would be to get busybox back on, and all relevant links reinstated. You've got a busybox in /mnt/initfs, but it's linked against a different libc, so you can't just drop it in here...

All I'm thinking is to rip busybox out of another system (on an SD, if you have one).

I have gtar and I have a SSH shell, but no ls, cp, etc. I manageed to gtar up my archives and /home directories. How do I use apt-get to install a local .deb in my archives directory? Yes I have busybox in /mnt/initfs/bin but I can't seem to execute anything there. I'm also running this OS off of SD, so I suppose I *could* reboot to the flash OS, mount the SD OS and ah, I'm freaking out, can you or anyone give me a roadmap or have I fubar?