From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lembark@wrkhors.com>
Message-ID: <3B02AC65.E6387069@wrkhors.com>
Date: Wed, 16 May 2001 11:35:49 -0500
From: Steven Lembark <lembark@wrkhors.com>
MIME-Version: 1.0
Subject: Re: [linux-lvm] LVM 1.0 release decision
References: <Pine.LNX.4.21.0105161241370.4671-100000@imladris.rielhome.conectiva>
Content-Transfer-Encoding: 7bit
Sender: linux-lvm-admin@sistina.com
Errors-To: linux-lvm-admin@sistina.com
Reply-To: linux-lvm@sistina.com
List-Help: <mailto:linux-lvm-request@sistina.com?subject=help>
List-Post: <mailto:linux-lvm@sistina.com>
List-Subscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=subscribe>
List-Unsubscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=unsubscribe>
List-Archive: <http://lists.sistina.com/pipermail/linux-lvm/>
List-Id: <linux-lvm.redhat.com>
Content-Type: text/plain; charset="us-ascii"
To: linux-lvm@sistina.com

> I'm all for it right now. I'm running LVM on practically all my
> machines and would really like to have the latest bugfixes in
> my kernel ;)

then grab the patches and apply them.  the main issue seems to 
be the rate at which LVM patches migrate into the stock distribution.
if you are running that much LVM it's likely that you already know
how to patch things to handle LVM in the first place.

-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582