Linux LVM users
 help / color / mirror / Atom feed
From: Stanley Yue <stanley.yue@gmail.com>
To: Stanley Yue <stanley.yue@gmail.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Resend: API for retrieving linux lvm information
Date: Wed, 8 Sep 2004 16:51:20 -0700	[thread overview]
Message-ID: <ce9f1f9e040908165111eff27f@mail.gmail.com> (raw)
In-Reply-To: <20040908093518.GC1094@agk.surrey.redhat.com>

Thanks, Alasdair.

I'll indeed look into using LVM2.

I'm using Redhat AS 3.0. 

Will the lvm2 rpm from Fedora Core work?
When will lvm2 be officially part of Redhat Enterprise Linux?
How can i upgrade from an LVM1 system to LVM2? Is it just a matter of
upgrading the rpm?

Thanks,

Stanley


On Wed, 8 Sep 2004 10:35:18 +0100, Alasdair G Kergon <agk@redhat.com> wrote:
> On Tue, Sep 07, 2004 at 06:39:24PM -0700, Stanley Yue wrote:
> > As far as the parsing goes, is it better (in terms of compatibility,
> > output stability) to parse against the command line output (i.e.
> > lvdisplay) or against the /proc/filesystems (i.e.
> > /proc/lvm/VGs/vg00/LVs)?
>  
> My answer was for LVM2.
> Looks like you're using LVM1.
> To simplify your future upgrade you should consider using LVM2 tools
> lvs/pvs/vgs read-only even on an LVM1 installation as their output is
> designed to be easy to parse.
> 
> Alasdair
> --
> agk@redhat.com
>

  reply	other threads:[~2004-09-08 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07  6:04 [linux-lvm] Resend: API for retrieving linux lvm information Stanley Yue
2004-09-07  9:44 ` Alasdair G Kergon
2004-09-08  1:39   ` Stanley Yue
2004-09-08  9:35     ` Alasdair G Kergon
2004-09-08 23:51       ` Stanley Yue [this message]
2005-07-13  9:03   ` Dieter Stüken

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=ce9f1f9e040908165111eff27f@mail.gmail.com \
    --to=stanley.yue@gmail.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