From: Jesus Manuel NAVARRO LOPEZ <jesus_navarro@promofinarsa.es>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm 1.0 and kernel 2.2.19.Is rawio patch necessary ??
Date: Thu, 04 Oct 2001 21:00:17 +0200 [thread overview]
Message-ID: <3BBCB1C1.92EE150F@promofinarsa.es> (raw)
In-Reply-To: 3BBCA384.EC6D4D53@ti.com
Hi again christian:
christian e wrote:
>
> christian e wrote:
>
> > I think I'll try the 2.2.18 patch as well..Will let you all know if it
> > turned out ok or not..
>
> Just tried the following:
>
> removed old kernel source tree,untarred a fresh 2.2.19 source.Did a
> ./configure in the lvm source dir.Then a make in the PATCHES DIR.Then
> applied the rawio patch for 2.2.18 and then the lvm-1.0 patch for my
> kernel 2.2.19.Patched clean without problems.
>
> Then compiled the kernel again.Then the modules..mind you I compiled lvm
> into the kernel not as module..No problems.
>
> Bootup withput problems (only forgetting to patch with aacraid driver
> but htat's another story :-)
>
> compiled lvm and installed..Works ok..
>
I had a fast day with some other snmp stuff so I didn't have time for
the LVM stuff. Only concern i I won't use root as LVM and it is stayed
that LVM should be compiled as a module preferably (I think coz the
developers don't considered that code so stable). Anyway, it seems that
we're near of a goal (at least, what's the problem with the de struct
member is allocated and pointed out to some 2.3.x kernel addition, so I
think it can be repaired for rc5 next week). Let's see...
In any case, thanks for your aid folks.
--
SALUD,
Jes�s
***
jesus_navarro@promofinarsa.es
***
next prev parent reply other threads:[~2001-10-04 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 12:24 [linux-lvm] lvm 1.0 and kernel 2.2.19.Is rawio patch necessary ?? christian e
2001-10-04 15:11 ` Jesus Manuel NAVARRO LOPEZ
2001-10-04 16:39 ` christian e
2001-10-04 17:59 ` christian e
2001-10-04 19:00 ` Jesus Manuel NAVARRO LOPEZ [this message]
2001-10-04 17:30 ` Joe Thornber
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=3BBCB1C1.92EE150F@promofinarsa.es \
--to=jesus_navarro@promofinarsa.es \
--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.