From: walter harms <wharms@bfs.de>
Cc: linux-hams@vger.kernel.org
Subject: Re: Soundmedem-.10 file not uncompressing
Date: Fri, 16 Nov 2007 10:10:47 +0100 [thread overview]
Message-ID: <473D5E97.20303@bfs.de> (raw)
In-Reply-To: <473C427A.2090000@ccr.jussieu.fr>
Bernard Pidoux wrote:
> Hi,
>
> I found that a simple "tar xvf" usually works, i.e. omitting the zip
> option (z for zip and j for zip2).
> So, you don't need to try "tar xvzf" and then "tar xvjf" if the first
> attempt fails.
>
> 73 de bernard, f6bvp
>
>
>
hi all,
the v option means only verbose but can test the file using t(z)f.
I test files always with vtzf to make sure that they do stay in a certain
directory and do not fill mit current working directory :)
re,
wh
prev parent reply other threads:[~2007-11-16 9: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
2007-11-15 12:58 ` Bernard Pidoux
2007-11-16 9:10 ` walter harms [this message]
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=473D5E97.20303@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