From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Chris Wedgwood <cw@f00f.org>
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 22:22:14 +0100 [thread overview]
Message-ID: <200605212222.14509.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20060521210056.GA3500@taniwha.stupidest.org>
On Sunday 21 May 2006 22:00, Chris Wedgwood wrote:
> On Sun, May 21, 2006 at 08:03:32PM +0100, Alistair John Strachan wrote:
> > Somebody needs to make lzma userspace tools (like p7zip) faster, not
> > crash, and behave like a regular UNIX program. Then we need a patch
> > to GNU tar to emerge, and for it to persist for at least 4
> > years. Then maybe people will adopt this format..
>
> why?
>
> the gains aren't that great
If it was less than 5%, I'd agree with you. The fact is, it's 17% better on a
regular kernel tarball (not exactly a contrived test), so there would be
reason to use it. It's also faster to decompress.
http://tukaani.org/lzma/
This utility appears to address most of my original concerns (i.e., it works
with stream LZMA and has a bzip2/gzip-esque frontend). I could see LZMA
replacing bzip2, but not gzip, due to the compression performance issues.
--
Cheers,
Alistair.
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-05-21 21:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 14:35 Justin Piszcz
2006-05-21 18:40 ` Jan Engelhardt
2006-05-21 18:56 ` Kasper Sandberg
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 [this message]
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=200605212222.14509.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=apiszcz@lucidpixels.com \
--cc=cw@f00f.org \
--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
all inboxes | Powered by JetHome®