public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: cryptoapi-devel@kerneli.org, linux-kernel@vger.kernel.org
Subject: Re: gcloop: compressed loopback support for 2.6
Date: Tue, 20 Jan 2004 00:15:24 +0100	[thread overview]
Message-ID: <400C650C.1070303@gentoo.org> (raw)
In-Reply-To: <20040119164139.GR1748@srv-lnx2600.matchmail.com>

Mike Fedyk wrote:
> On Mon, Jan 19, 2004 at 05:29:21PM +0100, Luca Barbato wrote:
> 
> 
> 
> Is/will knoppix be using this this as well or is this a fork?
> 
This started as fork from the cloop-0.6x.
Now the file format is almost the same, but the code is quite different: 
the only thing that remains is the the basic logic and the block unpacker.
The current code is currently under testing for gentoo livecd and other 
projects that use the same tecnology, at least that I'm aware.
If Klaus thinks that gcloop is good enough for his knoppix I'd be glad.

Currently gcloop-0.99 uses 32bit indexes since my target are livecd, for 
livedvd would be better use the newer cloop-2.0/1.0 file format with 
64bit indexes.

gcloop isn't file format compatible with the old cloop-0.68 fileformat 
since I had to use in a different way the index and I prefer ucl instead 
of zlib.

lu

-- 
Luca Barbato
Developer
Gentoo Linux				http://www.gentoo.org/~lu_zero



  reply	other threads:[~2004-01-19 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 16:21 cryptoloop extended for compressors Luca Barbato
2004-01-19 16:29 ` gcloop: compressed loopback support for 2.6 Luca Barbato
2004-01-19 16:41   ` Mike Fedyk
2004-01-19 23:15     ` Luca Barbato [this message]
2004-01-19 23:25       ` Mike Fedyk
     [not found]         ` <400C6AA2.4000307@gentoo.org>
2004-01-20  0:23           ` Mike Fedyk

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=400C650C.1070303@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=cryptoapi-devel@kerneli.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    /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