OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Software => Topic started by: sdjf on December 25, 2005, 09:33:44 am
-
Can someone tell me how to recover files that were in the command line editor when it terminated unexpectedly?
They always are in the /tmp directory
and have names starting with elv. Sorry I can't give exact format of file names but don't have any there now. Have tried viewing them as text and they clearly are machine code of some sort. Googling at the time I had them didn't help as our filenames are different than what I found.
Thanks!
sdjf
-
Have a look here (http://elvis.the-little-red-haired-girl.org/elvisman/elvisses.html).
-
Little red haired girl page makes more sense than the other pages I found. Saved page image and will test it next time it occurs.
BTW, where are the system files it mentions? Haven't seen anything resembling the file names it mentions.
Thank you,
sdjf
-
Have a look here (http://elvis.the-little-red-haired-girl.org/elvisman/elvisses.html).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=108446\"][{POST_SNAPBACK}][/a][/div]
I did and it didn't help. I have elvis vers. 1.4 and the commands suggested like :buffer which was not recognized by either elvis or bash, and also using the -r option didn't work.
Here's some of my activity:
bash-2.05# elvis -vvv
"/tmp/elv00dc31f01" is busy
bash-2.05# which elvis.ini
bash-2.05# elvis -r -Gquit
Use the `virec` program to recover lost files
bash-2.05# elvis -Gquit
"/tmp/elv00dc31f01" is busy
bash-2.05#
bash-2.05# vi -help
"/tmp/elv00dc31f01" is busy
bash-2.05#
bash-2.05# virec
bash: virec: command not found
bash-2.05#
bash-2.05# vi
"/tmp/elv00dc31f01" is busy
bash-2.05# elvis
"/tmp/elv00dc31f01" is busy
bash-2.05#
Suggestion to edit elvis.ini useless as:
bash-2.05# find elvis.ini
find: elvis.ini: No such file or directory
bash-2.05#
What next?
sdjf
-
You might try running:
find / -name elvis.ini
-
Yep, did it...and now what? It's gotta have another name or maybe could it just be binary?
bash-2.05# find / -name elvis.ini
find: /proc/12/fd: No such file or directory
bash-2.05#
tried with vi.ini for the heck of it, and same results:
bash-2.05# find / -name vi.ini
find: /proc/12/fd: No such file or directory
bash-2.05#
And here's proof the code was okay, hunting for a file I know I have.
bash-2.05# find / -name opera.ini
/home/root/.opera/opera.ini
find: /proc/12/fd: No such file or directory
bash-2.05#
Tried looking in /dev but that just got rid of the /proc/12/fd message:
bash-2.05# find //dev/ -name elvis.ini
bash-2.05#
sdjf