All of lore.kernel.org
 help / color / mirror / Atom feed
From: paddy <paddy@panici.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 on hardware RAID
Date: Tue, 15 Aug 2006 00:46:15 +0100	[thread overview]
Message-ID: <20060814234537.GF11767@cobalt0.panici.net> (raw)
In-Reply-To: <44E0FFE7.6070202@cantab.net>

On Mon, Aug 14, 2006 at 11:57:43PM +0100, Zak Kipling wrote:
> paddy wrote:
> 
> > I dont' have a pvresize or a pvextend, what version are you guys using ?
> 
> pvresize should be in 2.02.00 and later, according to WHATS_NEW.
> 
> I'm puzzled that you can't find it in etch (testing) though, since
> (according to packages.debian.org) it has 2.02.06 -- and the files list
> for the package includes /lib/lvm-200/pvresize. Sarge (stable), however,
> only has 2.01.04 which won't have pvresize.

ok, turns out I have 2.01.04-5 on that box.  I looked at packages.debian.org
and I agree that's what it says, and the developer info says it migrated in 
june ...

ok ... how's this for daft ...

# apt-get update
# dselect select

perhaps if I 'dselect update' ?

(better yet, I'd better get used to aptitude, which is a shame 'cos I like
dselect)

mystery solved.

Thanks!

(I'll go take a look at the code now, see if it's as simple as I thought :-)

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall

  reply	other threads:[~2006-08-14 23:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 19:37 RE: [linux-lvm] LVM2 on hardware RAID Musil, William
2006-08-14 22:36 ` paddy
2006-08-14 22:57   ` Zak Kipling
2006-08-14 23:46     ` paddy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-11 16:48 Musil, William
2006-08-11 17:24 ` paddy
2006-08-11 19:26 ` Greg Hartzog
2006-08-14 20:55   ` paddy

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=20060814234537.GF11767@cobalt0.panici.net \
    --to=paddy@panici.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.