public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-kernel@vger.kernel.org, apiszcz@lucidpixels.com
Subject: Re: Linux Kernel Source Compression
Date: Sun, 21 May 2006 20:56:17 +0200	[thread overview]
Message-ID: <1148237777.28518.0.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0605212026570.6083@yvahk01.tjqt.qr>

On Sun, 2006-05-21 at 20:40 +0200, Jan Engelhardt wrote:
> >
> > Was curious as to which utilities would offer the best compression ratio for
> > the kernel source, I thought it'd be bzip2 or rar but lzma wins, roughly 6 MiB
> > smaller than bzip2.
> >
> You forgot:
>   - .7z    7zip
>   - .j     JAR (www.arjsoftware.com)
>   - .ice   LHICE (some sort of "brother" to lharc aka lzh)
>   - .ace   ACE (www.winace.com)
>   -        UPX (yes!, you just need to put '#!/\n' at the front)
>   - .cab   MS CAB (use winace)
>   - .bh    BlackHole
>   - .pak   PKARC 2.51
>   - .sqz   SqueezeIt
>   - "LZEXE"
and also lzx, which was, in the amige days the best there was, allthough
i know of no compressor for linux

> 
> ftp://camelot.spsl.nsc.ru/pub/win32/arc/ - you'll find some there
> happy packing :)
> 
> > 38064   linux-2.6.16.17.tar.rz
> 
>   - is this rzip with _maximum_ distance?
> 
> 
> Jan Engelhardt


  reply	other threads:[~2006-05-21 18:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 14:35 Linux Kernel Source Compression Justin Piszcz
2006-05-21 18:40 ` Jan Engelhardt
2006-05-21 18:56   ` Kasper Sandberg [this message]
2006-05-21 19:28   ` Justin Piszcz
2006-05-22  2:05     ` Stefan Smietanowski
2006-05-21 19:03 ` Alistair John Strachan
2006-05-21 21:00   ` Chris Wedgwood
2006-05-21 21:22     ` Alistair John Strachan
2006-05-21 21:42     ` Sam Vilain
2006-05-21 21:57       ` Alistair John Strachan
2006-05-21 22:22         ` Sam Vilain
2006-05-21 22:29           ` Alistair John Strachan
2006-05-22 19:00             ` H. Peter Anvin
2006-05-21 21:59       ` Diego Calleja
2006-05-22 18:58   ` H. Peter Anvin
2006-05-22 19:07     ` Alistair John Strachan
2006-05-22 19:10       ` H. Peter Anvin
2006-05-22 19:15         ` Alistair John Strachan
2006-05-22 20:24           ` Jan Engelhardt
2006-05-22 20:41             ` H. Peter Anvin
2006-05-22 21:00             ` Alistair John Strachan
2006-05-22 21:04               ` H. Peter Anvin
2006-05-22 21:11                 ` Joshua Hudson
2006-05-23 13:37                 ` Jan Engelhardt
2006-05-23  2:16               ` Nuri Jawad
2006-05-23  2:55                 ` Stefan Smietanowski
2006-05-23 14:15                 ` Ivan Novick
2006-05-23 14:23                   ` Olivier Galibert
2006-05-23 14:47                     ` Julian Seward
2006-05-23 16:35                       ` Nuri Jawad
2006-05-25 11:42                     ` Jan Engelhardt
2006-05-31 22:51                 ` Bill Davidsen
2006-05-23 13:38               ` Jan Engelhardt
2006-05-23 15:28                 ` Alistair John Strachan
2006-05-31 22:56           ` Bill Davidsen
2006-05-26  4:11 ` Bruce Guenter

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=1148237777.28518.0.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=apiszcz@lucidpixels.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@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