From: Francis SOUYRI <francis.souyri@wanadoo.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] 2.4 LVM1 devfs -> 2.6.0 LVM2 devfs
Date: Mon Dec 22 00:20:02 2003 [thread overview]
Message-ID: <3FE68CE7.2030408@wanadoo.fr> (raw)
In-Reply-To: <20031220155700.GB21133@tykepenguin.com>
Hi Patrick
Thank yo, I'll try to implement the same installation on my system (no
Debian).
Best regards.
Francis
Patrick Caulfield wrote:
>On Sat, Dec 20, 2003 at 11:10:42AM +0100, Francis SOUYRI wrote:
>
>
>>Hi Patrick,
>>
>>I have a full ("/" is also a logical volume) LVM1 2.4 devfs system, and
>>I want to test the LVM2 2.6 devfs kernel.
>>
>>I want to have the possibility to boot the 2.4 or the 2.6 kernel with
>>the same filesystems.
>>
>>You say "lvm-common will detect whether you have device-mapper or LVM1
>>in the kernel and use the appropriate LVM tools". What is lvm-common ?
>>And if lvm-common can use the appropriate LVM tools how to install the
>>LVM1 and LVM2 tools in the same filesystem ("same" binaries)
>>
>>
>
>lvm-common is the Debian package that switches between LVM versions on the
>same system. If you install the "lvm10" or "lvm2" packages then this will get
>installed by default.
>
>The Debian LVM binaries get installded lib /lib/lvm-<version> and lvm-common
>decides at run-tim which one is the most appropriate to use.
>
>Of course you must use the Debian packages to get this, if you build your own
>tools from source then you're on your own :) (building your own kernels is fine
>though)
>
>
next prev parent reply other threads:[~2003-12-22 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 6:34 [linux-lvm] 2.4 LVM1 devfs -> 2.6.0 LVM2 udev Xavier Brouckaert
2003-12-19 7:26 ` Patrick Caulfield
2003-12-20 4:11 ` [linux-lvm] 2.4 LVM1 devfs -> 2.6.0 LVM2 devfs Francis SOUYRI
2003-12-20 9:58 ` Patrick Caulfield
2003-12-22 0:20 ` Francis SOUYRI [this message]
2003-12-22 2:09 ` Patrick Caulfield
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=3FE68CE7.2030408@wanadoo.fr \
--to=francis.souyri@wanadoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.