From: Joe Thornber <thornber@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] thin-provisioning-tools not part of lvm?
Date: Fri, 17 May 2013 15:49:06 +0100 [thread overview]
Message-ID: <20130517144905.GA21204@debian> (raw)
In-Reply-To: <51963E47.8060000@ubuntu.com>
On Fri, May 17, 2013 at 10:27:19AM -0400, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Why are helper programs required for lvm to use thin provisioning
> volumes not part of the lvm source package?
a) Because the whole point of device-mapper is it doesn't tie you in to a
single volume manager. Unfortunately EVMS doesn't seem to be
developed any more, so LVM2 has become the defacto choice.
b) Because the LVM2 codebase is too big and riddled with closely
coupled code that means making any changes takes forever.
- Joe
prev parent reply other threads:[~2013-05-17 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 14:27 [linux-lvm] thin-provisioning-tools not part of lvm? Phillip Susi
2013-05-17 14:49 ` Joe Thornber [this message]
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=20130517144905.GA21204@debian \
--to=thornber@redhat.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).