From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] libLVM progress?
Date: Thu, 26 Jul 2007 21:08:58 +0100 [thread overview]
Message-ID: <20070726200858.GL459@agk.fab.redhat.com> (raw)
In-Reply-To: <63576.192.52.57.33.1185480057.squirrel@webmail.wpi.edu>
On Thu, Jul 26, 2007 at 04:00:57PM -0400, Ken Stein wrote:
> * use a premade LVM interface library.
> The last idea came to me when I realized almost everything has a library
> these days, so I looked into it, but all I can find is people saying the
> current/old liblvm should not be used for new development or as a platform
> to base any new liblvm work off of, and people suggesting that a liblvm
> project be started to work with the new LVM systems and export a stable,
> logical public API. However, I can't find any mention of actual work
> being done on this - if I'm just missing it, a link would be great.
> Otherwise, is there any work I can base a modern liblvm implementation off
> of, or anyone I can talk to about joining a liblvm project to help out?
Work has begun.
The first step is to achieve proper separation of the 'tools' and 'lib'
directories - so the 'tools' directory will only use the new library
interface. If you watch the lvm-devel list you'll see a number of
patches going into the tree and the new interface evolving. Feel free
to help out on the lvm-devel mailing list.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2007-07-26 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 20:00 [linux-lvm] libLVM progress? Ken Stein
2007-07-26 20:08 ` Alasdair G Kergon [this message]
2007-07-26 20:09 ` Bryn M. Reeves
2007-07-30 14:40 ` Ken Stein
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=20070726200858.GL459@agk.fab.redhat.com \
--to=agk@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).