From mboxrd@z Thu Jan 1 00:00:00 1970 From: walter harms Subject: Re: Soundmedem-.10 file not uncompressing Date: Sun, 11 Nov 2007 11:10:16 +0100 Message-ID: <4736D508.6070608@bfs.de> References: Reply-To: wharms@bfs.de Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-hams-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-hams@vger.kernel.org hi all, instead of guessing you can identify the file using the 'file' utility. eg. file archive.tar.gz archive.tar.gz: gzip compressed data, from Unix file libsx-2.06.tar.bz2 libsx-2.06.tar.bz2: bzip2 compressed data, block size = 900k it is much more reliable then hoping that the suffix will give a hint. e.g. mv foo.tar.gz foo.tar.bz2 (note: i have seen people doing that) re, walter Frank Brickle wrote: > The convention is, .tgz for .tar.gz and therefore gzip; .tbz for > .tar.bz2 and therefore bzip2. > > 73 > Frank > AB2KT > > On Nov 10, 2007 10:05 PM, IT2 Stuart Blake Tener, USNR > wrote: >> Mr. Bricle, et alia: >> >> Indeed it is particularly instructive to note that the "tar zxvf >> name-of-your-gzipped-tarball" is presumptive to the fact that indeed the >> tarball has been size reduced with gzip! >> >> It is entirely possible to use "j" (vice little "z") for bzip, or even >> to use "Z" (big "Z") for compress/uncompress as appropriate. >> >> >> V/R, >> >> Stuart, N3GWG >> >> >> On 11/10/07 12:39 AM, "Frank Brickle" wrote: >> >>> Did you use the command >>> tar zxvf name-of-your-gzipped-tarball >>> ?