Linux LVM users
 help / color / mirror / Atom feed
From: David Brown <lvm@davidb.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Very long startup times of the lv*-tools
Date: Thu, 30 Dec 2004 11:17:29 -0800	[thread overview]
Message-ID: <20041230191729.GA5229@old.davidb.org> (raw)
In-Reply-To: <20041230191239.GW26670@agk.surrey.redhat.com>

On Thu, Dec 30, 2004 at 07:12:39PM +0000, Alasdair G Kergon wrote:
> On Wed, Dec 29, 2004 at 05:42:04PM +0100, Erik Wasser wrote:
> > I'm using lvm2 2.00.08 on a 'Linux fuzz 2.6.9-gentoo-r13 #1 Wed Dec 29 
> > 10:41:06 CET 2004 i686 AMD Athlon(tm) XP 2800+ AuthenticAMD GNU/Linux'
>  
> > Is there is something known about this issue? What else can I check?
>  
> Upgrade LVM2!
> 
> Anyone know why so many gentoo users find themselves using old 
> versions like that and don't upgrade?
> I don't see this with Debian or Fedora users.

Because the gentoo developers are very timid in marking new versions of
packages as stable.  This philosophy works well for packages that are
mostly stable.  It doesn't work all that well with things that are being
improved rapidly, such as lvm.

Putting the following lines in /etc/portage/package.keywords will cause
gentoo to use the newest versions of these packages:

  sys-libs/device-mapper ~x86
  sys-fs/lvm2 ~x86

Interestingly, the kernel mentioned is rather update on the kernel patches.

Dave

  reply	other threads:[~2004-12-30 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 16:42 [linux-lvm] Very long startup times of the lv*-tools Erik Wasser
2004-12-30 19:12 ` Alasdair G Kergon
2004-12-30 19:17   ` David Brown [this message]
2004-12-30 19:20   ` Jani Averbach
2004-12-30 19:28     ` Alasdair G Kergon
2005-01-01 14:20   ` Erik Wasser

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=20041230191729.GA5229@old.davidb.org \
    --to=lvm@davidb.org \
    --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