>If I issue the command as you've given it above, I get the same block
>size error. ...
Good. That means you have a valid test case.
>If I change the 2 to a 4, it does the same. ...
OK.
>If I remove
>the b and the 2 all-together, it them waits for the image file from
>stdin (I guess). ...
OK. Then 'b'/'2' is evil for your restore (miserable vendors :-).
>I'm a little ignorant as far as `restore` goes and am
>not sure how to feed it the image file in this situation.
It's not really important as we're just trying to figure out the command
line syntax. But if you wanted (needed) to do the real thing, it
would be something like:
ssh amanda-server /path/to/amrestore -p $TAPE the-client the-disk \
| /sbin/restore xf - /file/to/restore ...
Or you could change 'x' to 'i' and leave off the files to restore.
That would put you in an interactive session where you could cd around
and add what you wanted to be extracted (much like amrecover).
>I'm sorry about needing to be spoon fed. ...
Not a problem (not even close).
>This is Digital Unix 4.0 (with the dump patch applied). It is using the
>plain system dump/restore as far as I know--/sbin/dump and /sbin/restore.
Not sure what "the dump patch" is, but be that as it may ...
The reason I asked about vdump is that the most recent Amanda sources
(actually, I did this quite a while ago) have code that says "if we are
using vrestore, don't use the 'b' option", i.e. the exact fix you need.
But that is based literally on the restore program being named "vrestore",
which doesn't seem to match your situation.
So it looks like Amanda needs yet another special vendor case for
this.
When you ran ./configure, at the top it said what type of OS you're using
(as far as ./configure is concerned). For instance:
checking host system type... sparc-sun-solaris2.6
checking target system type... sparc-sun-solaris2.6
checking build system type... sparc-sun-solaris2.6
What did yours say?
>EZ
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
