From: Bill Davidsen <davidsen@tmr.com>
To: Nuri Jawad <lkml@jawad.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Source Compression
Date: Wed, 31 May 2006 18:51:48 -0400 [thread overview]
Message-ID: <447E1E04.5060509@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605230407320.25860@pc>
Nuri Jawad wrote:
> Hi,
> just wanted to remark that I never liked that bzip was replaced by bzip2
> (were there license issues?) since bzip's compression was/is often
> stronger:
>
> 39843104 Mar 28 09:33 linux-2.6.15.7.tar.bz2
> 39423739 Mar 28 09:33 linux-2.6.15.7.tar.bz
>
> Not a big difference in this case but still a step back. I for once am
> keeping my bzip binary.. does anyone know where the source can still be
> found?
I know I have a copy backed up, but I'm rather disorganized at the
moment, having moved two out-of-town offices into this one, after
spending 12 years on a ten week contract... but I doubt you want it,
it's slow as hell and violates all manner of patents. Mind you, I think
the patents are held by IBM, so they might be negotiable, but I think
the original is dead. Used either fractal or arithmetic compression IIRC.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-05-31 22:50 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
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 [this message]
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=447E1E04.5060509@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@jawad.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.