From: Phillip Susi <psusi@cfl.rr.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Willy Tarreau <w@1wt.eu>,
Drew Scott Daniels <ddaniels@UMAlumni.mb.ca>,
linux-kernel@vger.kernel.org
Subject: Re: Smaller compressed kernel source tarballs?
Date: Tue, 03 Oct 2006 14:24:01 -0400 [thread overview]
Message-ID: <4522AAC1.7050703@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0610031227420.32633@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> There are lots of obscure compression formats that achieve somewhat
> better compression at the cost of MUCH more time (neglecting they are
> not too open), such as MS CAB and ACE.
CAB is an archive container format, not a compression algorithm. Last
time I worked on some code to handle it, they used the standard LZW
algorithm implemented by gzip ( but had the ability to support others in
the future ) and could only compress 32kb blocks. The small block size
led to poor compression.
next prev parent reply other threads:[~2006-10-03 18:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 3:35 Smaller compressed kernel source tarballs? Drew Scott Daniels
2006-10-02 3:32 ` Bernd Eckenfels
2006-10-02 3:35 ` Willy Tarreau
[not found] ` <Pi ne.LNX.4.63.0610012205280.28534@qynat.qvtvafvgr.pbz>
2006-10-02 5:11 ` David Lang
2006-10-02 5:49 ` Willy Tarreau
2006-10-02 15:16 ` Phillip Susi
2006-10-02 15:48 ` David Lang
2006-10-02 20:20 ` Phillip Susi
2006-10-02 20:12 ` David Lang
2006-10-02 20:35 ` Willy Tarreau
[not found] ` <2006 1002203527.GA585@1wt.eu>
2006-10-02 21:49 ` Sean
[not found] ` <20061002174938.bb82027d.seanlkml@sympatico.ca>
2006-10-02 21:42 ` David Lang
2006-10-03 2:48 ` Willy Tarreau
2006-10-03 10:28 ` Jan Engelhardt
2006-10-03 18:24 ` Phillip Susi [this message]
2006-10-04 15:57 ` Compressing pages [was: Re: Smaller compressed kernel source tarballs?] Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 20:32 Smaller compressed kernel source tarballs? Dax Kelson
[not found] ` <20060921204250 .GN13641@csclub.uwaterloo.ca>
2006-09-21 20:42 ` Lennart Sorensen
[not found] ` <20060921171747.9ae2b42e.seanlkml@sympatico.ca>
2006-09-21 21:17 ` Sean
2006-09-21 21:41 ` Dax Kelson
2006-09-21 21:50 ` Bob Copeland
[not found] ` <20060921175717.272c58ee.seanlkml@sympatico.ca>
2006-09-21 21:57 ` Sean
2006-09-21 22:00 ` David Lang
2006-09-21 22:24 ` Dave Jones
2006-09-21 22:16 ` David Lang
2006-09-21 22:40 ` Dave Jones
2006-09-21 22:34 ` David Lang
[not found] ` <20060921193823.ec49d446.seanlkml@sympatico.ca>
2006-09-21 23:38 ` Sean
[not found] ` <Pin e.LNX.4.63.0609211455570.17238@qynat.qvtvafvgr.pbz>
2006-09-21 22:25 ` Sean
[not found] ` <20060921182554.23044ca3.seanlkml@sympatico.ca>
2006-09-21 22:20 ` David Lang
2006-09-21 21:40 ` Dax Kelson
2006-09-22 14:00 ` Lennart Sorensen
2006-09-21 21:43 ` H. Peter Anvin
2006-09-22 14:00 ` Lennart Sorensen
2006-09-22 16:13 ` H. Peter Anvin
2006-09-22 16:13 ` Jan Engelhardt
2006-09-22 16:33 ` H. Peter Anvin
2006-09-22 17:41 ` Johannes Stezenbach
2006-09-22 18:09 ` H. Peter Anvin
2006-09-22 18:19 ` Michael Tokarev
2006-09-22 18:26 ` H. Peter Anvin
2006-09-25 11:51 ` Paulo Marques
2006-09-25 15:47 ` H. Peter Anvin
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=4522AAC1.7050703@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=ddaniels@UMAlumni.mb.ca \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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