From: Mark Borges <mdb@cdc.noaa.gov>
Subject: Re: compressed nnfolder archives
Date: 23 Jul 1996 15:27:31 -0600 [thread overview]
Message-ID: <vkspaimzi4.fsf@cdc.noaa.gov> (raw)
In-Reply-To: Richard Pieri's message of 23 Jul 1996 09:41:10 -0400
>> On 23 Jul 1996 09:41:10 -0400,
>> Richard Pieri(RP) wrote:
RP> on-the-fly compression schemes (crypt++, jka-compr) likewise are
RP> also never invoked. Renaming the file to remove the compression
RP> extension will fail because the compression schemes use the
RP> extension to determine compression type, if any.
Not quite correct.
jka-compr relies on the extension, but crypt++ does not. It peeks
inside the file and uses a magic number technique. I've used crypt++
to automagically decode many gzip'd files w/o the `.gz' filename
extension.
--
-mb-
next prev parent reply other threads:[~1996-07-23 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-23 6:30 Erik Selberg
[not found] ` <x7viff9jex.fsf@unilab.dfci.harvard.edu>
1996-07-23 21:27 ` Mark Borges [this message]
1996-07-24 5:51 ` Andy Eskilsson
1996-07-24 13:34 ` Richard Pieri
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=vkspaimzi4.fsf@cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
/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;
as well as URLs for NNTP newsgroup(s).