From: Scott Castaline <skotchman@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt Digest, Vol 9, Issue 4
Date: Thu, 04 Mar 2010 17:59:40 -0500 [thread overview]
Message-ID: <4B903B5C.70404@gmail.com> (raw)
In-Reply-To: <mailman.1.1267700401.18882.dm-crypt@saout.de>
> Today's Topics:
>
> 1. Re2: reading archives (Arno Wagner)
> 2. reading archives (Scott Castaline)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 4 Mar 2010 01:31:16 +0100
> From: Arno Wagner<arno@wagner.name>
> To: dm-crypt@saout.de
> Cc: christophe@saout.de
> Subject: [dm-crypt] Re2: reading archives
> Message-ID:<20100304003116.GA1196@tansi.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> Ok, I looked a bit closer. It seems this is compressed
> on-the-fly and corrupted on server side. Strangely
> the corruption seems to be a windows thing or at least
> browser dependent. I got suspicuous after I got two
> different sized files with Opera and Firefox. On
> Linux I downloaded with wget for yet another size.
>
> After a bit of messing around, I have it now:
> Under Windows the files get compressed with gzip
> twice! Possibly some terminally stupid, over-helpful
> automatisation that decided to make sure it is a
> gzip'ed file.
>
> Temporary workaround for Windows:
>
> Decompress, rename to name.gz and decompress again.
> You may also have to click through a folder hierachy
> (that I had no idea gzip could support).
>
> Admin of the archive cc'ed, just in case.
>
> Arno
>
Ok, doing gzip twice was the trick, I can now read the archives from Aug
09 to Jan 10. Are you doing the list on a Windows Server? I've zipped
files on Linux many times and never ran into this bug of double packing
before. I did wonder about the fact that the 1st unpacking produced the
same size file that the size didn't change until the 2nd go around.
parent reply other threads:[~2010-03-04 22:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.1.1267700401.18882.dm-crypt@saout.de>]
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=4B903B5C.70404@gmail.com \
--to=skotchman@gmail.com \
--cc=dm-crypt@saout.de \
/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