Well I discovered that the cygwin created tar file requires a z (uncompress)
switch to untar.
This was a little confusing as I never specified the z (compress) when the
archive was created, so some form of compression may be a default.
However, it know appears to be untarring fine on the Mandrake box.
It was late in the evening...
"Nigel Hammond" [hammondnigel@blueyonder.co.uk] wrote in message
news:aS33e.7307$r47.2128@fe3.news.blueyonder.co.uk...
Hi,
I've created some tar (and gzipped) files using Cygwin on Win2K, using the
above
version of tar.
Standard command used: tar -cvf .... someFile.tar
someFile.tar was the ftp across (using binary transfer WuFtp daemon, ftp GNU
inetutils v1.3.2 client) to the Mandrake82 box.
When I attempted: tar -xvf someFile.tar
I got messages:
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains onsolescent base-64 headers
Do I have to specify special options to make a compatible format between the
two
operating systems?
I though that tar may be fairly standard (although I noticed WinZup on Windows
didn't create tar files).
Perhaps someone may suggest a better way for me to transfer the files across
the
machines, although I hoped this would be fairly straightforward.
regards nigel
The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.