Greetings, Murthy Gandikota! >>> anything except make a LARGER file - because the first round of >>> compression removed any redundancy). Tar cannot read a >>> double-compressed stream, but breaking things into two steps lets you >>> get back to a single compressed stream, where the tar call then >>> auto-decompresses because you weren't supplying an explicit 'z' the >>> second time around. To prove it, try: >>> >>> gunzip <mytar.gz>mytar >>> tar zxvf mytar >>> >>> and if it still untars with an explicit decompression, then you have >>> proven that your original file was double-compressed. Also, if I'm >>> right about double compression, then mytar.gz would likely be slightly >>> larger than mytar (rather than the usual case of the .gz being >>> noticeably smaller). >> >> Yes, Sir. It did untar properly. So the problem is with the server >> compressing during the download (I get the file from a http server)? >> Thanks a lot for your help
> It would be doubly nice if cygwin handled it ;-) It seems gunzip had no > problem recognizing the file as double compressed. > Thanks all for the help. This is not expected, nor supported. And is unlikely to ever be supported. Adding "support" for such cases would easily create a shell bomb, if you nest packers enough times. -- With best regards, Andrey Repin Tuesday, April 21, 2015 02:31:44 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
