tar cf – * | ( cd /target; tar xfBp -)

Anonymous wrote:

Not always, no.

for instance I recently used this to do a full path copy of some contents on a bad cdrom. For whatever reason I needed the entire path. So I did a variation and put it into a script so I could use it later. It went like this:

#!/bin/bash

find $1 | while read i;
do tar cfv – $i | ( cd $2 ; tar xfpv – )
done

So I could do something like this on the command line:

fullpathcp /dvd/Examples ~/tmp/copy

probably not the best use of cpu resources, but I got plenty of cycles to spare.

Also you can do interesting things with variations of this.

Like if your on a ftp server and they have a ls.gz file. This lists the contents of the server so you can go like this:

ftp server blah
username:anonymous
anonymous login ok. Please give E-mail address
password:
> get ls.gz “|gunzip – |less”
or
> get ls.gz “|gunzip – |grep p0rn”

And that way you can scroll around up and down. Or untar a file and download it onto your system…
> get big.fat.tar.gz “| (cd ~/tmp/ ; tar zxf -)”

or at least something similar.

Also you can use Netcat to transfer files similar to that and so on and so forth. It’s but one peice in a puzzle you need to build bigger and better scripts. ]]> http://www.tech-recipes.com/rx/115/copy-files-and-directories-recursively-with-tar/comment-page-1/#comment-240 Anonymous Mon, 12 Jul 2004 04:21:18 +0000 guid-fix-me!#comment-240 Not always, no. for instance I recently used this to do a full path copy of some contents on a bad cdrom. For whatever reason I needed the entire path. So I did a variation and put it into a script so I could use it later. It went like this: #!/bin/bash find $1 | while read i; do tar cfv - $i | ( cd $2 ; tar xfpv - ) done So I could do something like this on the command line: fullpathcp /dvd/Examples ~/tmp/copy probably not the best use of cpu resources, but I got plenty of cycles to spare. Also you can do interesting things with variations of this. Like if your on a ftp server and they have a ls.gz file. This lists the contents of the server so you can go like this: ftp server blah username:anonymous anonymous login ok. Please give E-mail address password: > get ls.gz "|gunzip - |less" or > get ls.gz "|gunzip - |grep p0rn" And that way you can scroll around up and down. Or untar a file and download it onto your system... > get big.fat.tar.gz "| (cd ~/tmp/ ; tar zxf -)" or at least something similar. Also you can use Netcat to transfer files similar to that and so on and so forth. It's but one peice in a puzzle you need to build bigger and better scripts. Not always, no.

for instance I recently used this to do a full path copy of some contents on a bad cdrom. For whatever reason I needed the entire path. So I did a variation and put it into a script so I could use it later. It went like this:

#!/bin/bash

find $1 | while read i;
do tar cfv – $i | ( cd $2 ; tar xfpv – )
done

So I could do something like this on the command line:

fullpathcp /dvd/Examples ~/tmp/copy

probably not the best use of cpu resources, but I got plenty of cycles to spare.

Also you can do interesting things with variations of this.

Like if your on a ftp server and they have a ls.gz file. This lists the contents of the server so you can go like this:

ftp server blah
username:anonymous
anonymous login ok. Please give E-mail address
password:
> get ls.gz “|gunzip – |less”
or
> get ls.gz “|gunzip – |grep p0rn”

And that way you can scroll around up and down. Or untar a file and download it onto your system…
> get big.fat.tar.gz “| (cd ~/tmp/ ; tar zxf -)”

or at least something similar.

Also you can use Netcat to transfer files similar to that and so on and so forth. It’s but one peice in a puzzle you need to build bigger and better scripts.

In Summary, I would recommend this instead:

tar cf - * .??* | ( cd /target; tar xfp -)

but first do:

ls -a

and if you see anything starting with a . (besides ..) that is not followed by more then two characters, add those as well e.g.

tar cf - * .??* .a .z .bc | ( cd /target; tar xfp -)