Linux LVM users
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] liblvm status question
Date: Tue, 17 Mar 2009 10:38:24 +0000	[thread overview]
Message-ID: <1237286304.10568.67.camel@breeves.fab.redhat.com> (raw)
In-Reply-To: <87f94c370903161358u16398431uac9f8e8ab3e0c17@mail.gmail.com>

On Mon, 2009-03-16 at 16:58 -0400, Greg Freemyer wrote:
> On Mon, Mar 16, 2009 at 3:55 PM, ben scott <benscott@nwlink.com> wrote:
> > Is the liblvm project at a state where vgs, lvs or pvs functionality is mostly
> > working? I am writing a program for working with logical volumes and it would
> > be very helpful if I could start integrating liblvm now even if it is still
> > buggy at the moment. Also, where can I  find the files or cvs?
> >
> > Thank you
> 
> I think you mean libdevmapper don't you?

No, he means liblvm:

http://fedoraproject.org/wiki/Features/liblvm
http://fedoraproject.org/wiki/LVM/liblvm

Patches are just starting to be merged but it's still a
work-in-progress:

http://www.redhat.com/archives/lvm-devel/2009-March/msg00008.html

Follow the lvm-devel mailing list to keep track of what's going on.

Regards,
Bryn.

  reply	other threads:[~2009-03-17 10:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 17:46 [linux-lvm] fsync() and LVM Marco Colombo
2009-03-13 20:08 ` Stuart D. Gathman
2009-03-13 20:29   ` Ben Chobot
2009-03-13 20:38   ` Alasdair G Kergon
2009-03-14  3:16     ` Marco Colombo
2009-03-14  9:07     ` Dietmar Maurer
2009-03-14 14:31       ` Stuart D. Gathman
2009-03-15  0:51         ` Marco Colombo
2009-03-16 11:02           ` Charles Marcus
2009-03-16 11:05             ` Martin Schröder
2009-03-16 11:18               ` Charles Marcus
2009-03-16 11:25                 ` Dietmar Maurer
2009-03-16 14:36             ` Marco Colombo
2009-03-16 17:13               ` Stuart D. Gathman
2009-03-16 17:17           ` Stuart D. Gathman
2009-03-16 18:50             ` Les Mikesell
2009-03-16 19:36               ` Greg Freemyer
2009-03-16 19:55                 ` [linux-lvm] liblvm status question ben scott
2009-03-16 20:58                   ` Greg Freemyer
2009-03-17 10:38                     ` Bryn M. Reeves [this message]
2009-03-17 18:42                       ` ben scott
2009-03-17 20:52                       ` Greg Freemyer
2009-03-16 20:28                 ` [linux-lvm] fsync() and LVM Les Mikesell
2009-03-16 20:54                   ` Greg Freemyer
2009-03-16 21:17                     ` Les Mikesell
2009-03-16 21:36                       ` Greg Freemyer
2009-03-16 21:53                         ` Les Mikesell
2009-03-16 22:51                           ` Joshua D. Drake
2009-03-17 15:33                             ` Joshua D. Drake
2009-03-19  9:20                               ` Tim Post
2009-03-16 21:57                         ` Allen, Jack
2009-03-17 16:00             ` Marco Colombo
2009-03-17 17:40               ` Stuart D. Gathman
2009-03-17 18:17                 ` Les Mikesell
2009-03-18  0:37                   ` Marco Colombo
2009-03-15  8:51         ` Dietmar Maurer
2009-03-15 23:31           ` Marco Colombo
2009-03-17 18:12           ` Les Mikesell
2009-03-17 18:19             ` Dietmar Maurer

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=1237286304.10568.67.camel@breeves.fab.redhat.com \
    --to=bmr@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