From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Shaun Savage <savages@tvlinux.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: CBD Compressed Block Device, New embedded block device
Date: Sun, 22 Jan 2006 19:26:03 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.4.61.0601221924410.17176@yvahk01.tjqt.qr> (raw)
In-Reply-To: <43D3A9D1.2060800@cfl.rr.com>
> How is this different from cloop or dm-crypt?
(dm-crypt is for crypting, CBD is for compression, I'd say.)
Compared to cloop, I'd say "the same" without giving too much thought away,
but as always - he who comes first, draws first.
Jan Engelhardt
--
next prev parent reply other threads:[~2006-01-22 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 8:46 CBD Compressed Block Device, New embedded block device Shaun Savage
2006-01-21 19:53 ` Arjan van de Ven
2006-01-21 21:09 ` Randy.Dunlap
2006-01-21 22:05 ` Alexey Dobriyan
2006-01-21 22:22 ` Matt Mackall
2006-01-22 8:26 ` Pavel Machek
2006-01-23 2:26 ` Shaun Savage
2006-01-22 15:50 ` Phillip Susi
2006-01-22 18:26 ` Jan Engelhardt [this message]
2006-01-23 11:34 ` Shaun Savage
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=Pine.LNX.4.61.0601221924410.17176@yvahk01.tjqt.qr \
--to=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=savages@tvlinux.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).