All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: jbradford@dial.pipex.com
Cc: Christian Ludwig <cl81@gmx.net>, linux-kernel@vger.kernel.org
Subject: Re: bzip2 patent status query
Date: Wed, 10 Jul 2002 13:26:26 -0400	[thread overview]
Message-ID: <20020710132626.A13654@mark.mielke.cc> (raw)
In-Reply-To: <200207101554.QAA07949@darkstar.example.net>; from jbradford@dial.pipex.com on Wed, Jul 10, 2002 at 04:54:51PM +0100

On Wed, Jul 10, 2002 at 04:54:51PM +0100, jbradford@dial.pipex.com wrote:
> Is bzip2 *definitely* patent-unencumbered?
> It claims to be on it's home page, but I found this from the OpenBSD people:
> http://www.openbsd.org/2.8_packages/m68k/bzip-0.21.tgz-long.html

If you read a little further on the bzip pages, you would find that the
reason bzip2 and bzip are incompatible, is because bzip was found to be
patent-encumbered. The search for a better compression algorithm, that
wasn't covered by a patent began...

I actually remember when the original sources for the block sorter
compression program were posted to comp.sources.misc or somewhere
similar. The original impression most people had was 'this algorithm
is a hoax... it can't compress...' And so, I believe, nobody bothered
to patent it. :-)

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  parent reply	other threads:[~2002-07-10 17:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 13:57 bzip2 support against 2.4.18 Christian Ludwig
2002-07-10 15:54 ` bzip2 patent status query jbradford
2002-07-10 16:48   ` Albert D. Cahalan
2002-07-10 17:37     ` jbradford
2002-07-10 17:08   ` Alan Cox
2002-07-10 17:26   ` Mark Mielke [this message]
2002-07-10 21:11   ` Rik van Riel
2002-07-12  7:04     ` Christian Ludwig
     [not found] ` <20020711062832.GU1548@niksula.cs.hut.fi>
2002-07-11  7:21   ` bzip2 support against 2.4.18 Christian Ludwig
2002-07-11 17:22     ` Daniel Phillips
2002-07-12  6:36       ` Christian Ludwig
2002-07-12  7:30         ` Daniel Phillips
2002-07-12  8:32           ` Christian Ludwig
2002-07-12  8:52             ` Daniel Phillips
2002-07-12 10:12               ` Christian Ludwig
2002-07-12 12:01                 ` jw schultz
2002-07-12 14:25               ` Tom Oehser
2002-07-12 14:49                 ` Mark Mielke
2002-07-15 21:31             ` Horst von Brand
2002-07-16 12:01               ` Tom Oehser
2002-07-12 12:37           ` Thunder from the hill
2002-07-13 13:56           ` john slee
2002-07-13 14:04             ` Daniel Phillips
2002-07-13 15:02               ` Tomas Szepe
2002-07-13 14:44             ` Thunder from the hill
2002-07-12 12:33         ` Thunder from the hill
2002-07-12 13:05         ` jbradford
2002-07-12 13:24         ` Mark Mielke
2002-07-12 13:49           ` Christian Ludwig
2002-07-12 14:21         ` Tom Oehser
2002-07-15  6:28           ` Christian Ludwig
2002-07-15 12:17             ` Tom Oehser
2002-07-16  8:28               ` [PATCH] bzip2 compression for kernel 2.4 and ramdisk Christian Ludwig
2002-07-13  5:16       ` bzip2 support against 2.4.18 Mike Touloumtzis

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=20020710132626.A13654@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=cl81@gmx.net \
    --cc=jbradford@dial.pipex.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 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.