From: "Steven Stillaway" <steve@stillaway.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: device-mapper transition
Date: Fri Oct 11 04:05:11 2002 [thread overview]
Message-ID: <20021011090446.GA5506@sparcbox.net> (raw)
In-Reply-To: <20021011075220.GA1153@fib011235813.fsnet.co.uk>
On Fri, Oct 11, 2002 at 08:52:21AM +0100, Joe Thornber wrote:
> If you do try 2.5 feedback would be appreciated.
>
> - Joe
>
After much time mostly spend trying to figure out how
bitkeeper works I have managed to get DM compiled and
working with 2.5.41
There were no problems compiling and it seems to be
working fine so far.
The only really tricky bit has been the fact that the
lvm tools (in particular vgscan) are completely
different between the two version. Actually LVM 2 just
seems to have one tool with a lot of symlinks.
So when I switch from 2.4.19 w/ LVM 1 to 2.5.41 w/
LVM2 I have to make sure to switch from one vgscan to
the other.
The obviously solution is to upgrade my 2.4.19 to
LVM2, but not tonight -- it is late.
If I notice anything I will let you know. If you
have any questions or want some data from my test
box please let me know.
Off to bed now -- later
--
Steven Stillaway
steve@stillaway.net
next prev parent reply other threads:[~2002-10-11 4:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1034276879.2396.11.camel@mars.goatskin.org>
2002-10-11 2:53 ` [linux-lvm] Re: device-mapper transition Joe Thornber
2002-10-11 4:05 ` Steven Stillaway [this message]
2002-10-11 4:25 ` [linux-lvm] device-mapper & proc Steven Stillaway
2002-10-11 4:48 ` Joe Thornber
2002-10-11 4:32 ` [linux-lvm] Re: device-mapper transition Joe Thornber
2002-10-11 17:09 ` Andres Salomon
2002-10-11 18:09 ` Alasdair G Kergon
2002-10-14 2:59 ` Heinz J . Mauelshagen
2002-10-12 12:30 ` Steven Stillaway
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=20021011090446.GA5506@sparcbox.net \
--to=steve@stillaway.net \
--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