Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm and Debian
Date: Fri Jan 18 07:06:02 2002	[thread overview]
Message-ID: <20020118140222.B794@sistina.com> (raw)
In-Reply-To: <20020118115639.GA30348@balu.kawo2.rwth-aachen.de>; from mdobel@kawo2.rwth-aachen.de on Fri, Jan 18, 2002 at 12:56:39PM +0100

On Fri, Jan 18, 2002 at 12:56:39PM +0100, Markus Dobel wrote:
> On Fri, Jan 18, 2002 at 11:58:03AM +0100, Pierrick PONS wrote:
> >
> > There's a thing I don't understand : is the lvm_1.0.1rc4 patch still in the 
> > 2.4.17 kernel or do I have to patch my 2.4.17 kernel to use lvm and lvm 
> > commands ?
> 
> There is some kind of LVM 1.0.1rc4 (therefore called 1.0.1rc4(ish)) in
> kernel 2.4.17.
> 
> > I thought that using a 2.4.17 kernel permitted to have lvm fonctionalities and 
> > not to be obliged to patch the kernel.
> 
> No, you don't *need* to patch the kernel to have LVM. It's in the
> kernel, just in an older version.

In case you want to go with LVM 1.0.1 (which is the actual release you
can get from www.sistina.com) and want to have the recent driver fixes
in the kernel as well, you still need to patch it following the instructions
in INSTALL and PATCHES/README.
1.0.1 for eg. addresses devfs and unresolved symbol issues.

> 
> Regards, Markus
> 
> -- 
> Free the Fluffy Bunny.
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-01-18  7:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18  4:31 [linux-lvm] lvm and Debian Pierrick PONS
2002-01-18  4:45 ` Markus Dobel
2002-01-18  4:59   ` Pierrick PONS
2002-01-18  5:19     ` Tom Brown
2002-01-18  5:57     ` Markus Dobel
2002-01-18  7:06       ` Heinz J . Mauelshagen [this message]
2002-01-18  8:00     ` Petro
2002-01-18  5:00 ` christian e
2002-01-18  5:05 ` Adrian Phillips
2002-01-18  5:25   ` Pierrick PONS
2002-01-18  5:38     ` Adrian Phillips
2002-01-18  5:53       ` Pierrick PONS
2002-01-18  5:42     ` Chris Danis
2002-01-18  5:47       ` Wichert Akkerman
2002-01-18  5:55         ` Adrian Phillips
2002-01-18  7:59 ` Petro
  -- strict thread matches above, loose matches on Subject: below --
1999-08-20 18:15 [linux-lvm] LVM " Drew Smith
1999-08-20 21:09 ` Ryan Murray
1999-08-20 22:41   ` Drew Smith
1999-08-23 14:12   ` Brian Wolfe
1999-08-24  7:44     ` Thomas Gebhardt

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=20020118140222.B794@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.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