From: walter harms <wharms@bfs.de>
To: linux-hams@vger.kernel.org
Subject: Re: Soundmedem-.10 file not uncompressing
Date: Sun, 11 Nov 2007 11:10:16 +0100 [thread overview]
Message-ID: <4736D508.6070608@bfs.de> (raw)
In-Reply-To: <fc22d18f0711101938p7dfe22dfna0e5a519eff44c1b@mail.gmail.com>
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
> <teners@bh90210.net> 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" <brickle@pobox.com> wrote:
>>
>>> Did you use the command
>>> tar zxvf name-of-your-gzipped-tarball
>>> ?
next prev parent reply other threads:[~2007-11-11 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 12:41 Soundmedem-.10 file not uncompressing Phil
2007-11-10 8:23 ` Bent
2007-11-10 8:39 ` Frank Brickle
2007-11-10 17:19 ` Phil
2007-11-11 16:49 ` don
2007-11-11 3:05 ` IT2 Stuart Blake Tener, USNR
2007-11-11 3:38 ` Frank Brickle
2007-11-11 10:10 ` walter harms [this message]
2007-11-15 12:58 ` Bernard Pidoux
2007-11-16 9:10 ` walter harms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4736D508.6070608@bfs.de \
--to=wharms@bfs.de \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox