From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: LVM Mailing List <linux-lvm@mlists.sistina.com>
Subject: [linux-lvm] Upgrade path
Date: Fri, 13 Jul 2001 09:26:26 -0300 [thread overview]
Message-ID: <3B4EE8F2.5050506@ednet.ns.ca> (raw)
Hello,
I am currently using LVM driver version 0.9.1_beta6 with a 2.2.19
kernel. I am planning to upgrade to kernel version 2.4.6 or maybe
2.4.7-pre6. What LVM version should I compile into the kernel? Should I
stay with 0.9.1_beta6 or jump up to 0.9.1_beta7? I did extend a logical
volume using 0.9.1_beta6 if that makes any difference.
next reply other threads:[~2001-07-13 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 12:26 Patrick Boutilier [this message]
2001-07-16 11:29 ` [linux-lvm] Upgrade path Heinz J. Mauelshagen
2001-07-16 12:03 ` Wichert Akkerman
2001-07-16 14:25 ` Heinz J. Mauelshagen
2001-07-16 14:42 ` Wichert Akkerman
2001-07-16 14:58 ` Joe Thornber
2001-07-17 11:31 ` Heinz J. Mauelshagen
2001-07-16 19:48 ` Heinz J. Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 20:11 Gonyou, Austin
2001-07-17 11:29 ` Heinz J. Mauelshagen
2003-03-20 15:48 Bradley M Alexander
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=3B4EE8F2.5050506@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--cc=linux-lvm@mlists.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