>... when I try to extract a file it asks me if I
>want to restore it to a <scrambled text> dir instead of the proper
>dir. What's wrong?
It's a bug (I'll fix it tomorrow). It should have repeated something
along the lines of this threat that "ls" showed you:
shell-init: could not get current directory: getcwd: cannot access
parent directories: No such file or directory
In other words, your current working directory is one that getcwd()
cannot figure out.
Just before you run amrecover, what does /bin/pwd (you must enter the
full path, don't just type "pwd") have to say?
>The sun versions were:
># dump -V
As Joshua mentioned, "dump" is not the file system backup program used
on Solaris. It's usually ufsdump.
>Is amrecover refusing to restore the file because it was dumped on
>solaris which has compatibility issues with the linux dump?
Why do you think it's refusing to restore the file? Your output stopped
at the bogus "Restoring into" message, but that should not have stopped
it from going on (unless amrecover died at that point).
However, also as Joshua said, system dump images are rarely compatible
between OS's, so if you're trying to restore a Solaris image on a Linux
box, it's probably not going to work.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
