Thanks very much for the help... > First make a scratch directory like this: > mkdir /var/tmp/testing/ > Then, from inside that directory, run the same dd command, but > with "gtar -tvf -" so you can see exactly which files got into > the archive. This also shows what the file names look like. They > won't start with a slash, because tar strips those, but they > probably will start with ./ depending on how tar was called. > > Ultimately, you'll probably need to use "gtar -xf - ./usr.dump" > > > And if the data transferred, where did it go to? Not to the directory wher I > > ran the dd command from... Did it get sent back to the client automagically? > > I wouldn't take the chance of overwritting something accidentally. > That's why I suggest you run the dd and tar commands from within > a new, empty directory.
I had originally make the scratch directory so as to avoid problems, and had been running the command from inside that directory. I followed your advice and ran the command with the -tvf - flags, which seemed to only give me a listing of directories.: # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -tvf - I grepped this for amanda, but only got the directories containing amanda then, of course, so finally I got on the ball and : # dd if=/dev/nrsa0 bs=32k skip=1 | /usr/local/bin/gtar -xf - ./home/user/amanda-2.4.2p2.tar.gz which gave me just what I wanted - THANKS! John LaBadie wrote: > It is a common unix convention to use "-" as a file name placeholder > meaning "standard input". For example: "ls | cat foo - bar" puts > the ls output between the contents of the files foo and bar. Didn't know that - that was one of the things that was confusing me, thanks for the clarification. Cheers much, Shawn
