From: Pierrick PONS <ppons@cvf.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm and Debian
Date: Fri Jan 18 04:59:01 2002 [thread overview]
Message-ID: <E16RWih-0000HQ-00@arwen.dev33.cvf> (raw)
In-Reply-To: Your message of "Fri, 18 Jan 2002 11:44:18 +0100." <20020118104418.GA29876@balu.kawo2.rwth-aachen.de>
> >
> > Am I obliged to use lvm_1.0.1-rc4 (that's the latest I found on Sistina web
> > site ) if I'm under a 2.4.17 kernel ?
>
> The text on http://www.sistina.com/products_lvm_download.htm is not up
> to date. There's 1.0.1 final already on the FTP server. Just follow the
> link to 1.0.1rc4.
>
> Although I did not have any problems with the 1.0.1rc4(ish) code in
> stock kernel 2.4.17, I'd recommend using 1.0.1.
>
> Regards, Markus
>
> --
> Free the Fluffy Bunny.
>
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 ?
I thought that using a 2.4.17 kernel permitted to have lvm fonctionalities and
not to be obliged to patch the kernel.
Sorry for my ignorance.
Pierrick
next prev parent reply other threads:[~2002-01-18 4:59 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 [this message]
2002-01-18 5:19 ` Tom Brown
2002-01-18 5:57 ` Markus Dobel
2002-01-18 7:06 ` Heinz J . Mauelshagen
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=E16RWih-0000HQ-00@arwen.dev33.cvf \
--to=ppons@cvf.fr \
--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