From: christian e <cej@ti.com>
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 18:39:37 +0200 [thread overview]
Message-ID: <3BBC90C9.309A3D75@ti.com> (raw)
In-Reply-To: 3BBC7C22.1119BF0@promofinarsa.es
Jesus Manuel NAVARRO LOPEZ wrote:
> Well, I'm in same position than you, but having problems.
> I also asked about the necesity of raw-io patches (specifically for
> 2.2.19) but till the moment no answer.
This concerns me if it's so important to patch with someone ought to
know..
I'm not keen on rolling this setup into production if I don't know the
consequences of not having a rawio patch applied (if any).
> Well, I patched kernel with raw-io for 2.2.18, and then with the lvm
> patch provided by ./configure then make at PATCHES, but my kernel didn't
> compile (well, the kernel did, but the make modules failed).
I think I'll try the 2.2.18 patch as well..Will let you all know if it
turned out ok or not..
>
> So, from your experience I'm going to try to compile *without* the
> raw-io patch and see what happens. Anyway, since I know that at least
> your compilation was ended with success, would you be kind enough to
> e-mail me your configuration file (/usr/src/linux/.config) to look for
> differencies?
You've got mail :-)
>
> And, if you know about the reason or necesity (or lack of) the raw-io
> patch stuff, please post it to the list, so others like will know.
> TIA
>
So far I haven't found out..If someone could enlighten us ,please ??
best regards
Christian
next prev parent reply other threads:[~2001-10-04 16:39 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 [this message]
2001-10-04 17:59 ` christian e
2001-10-04 19:00 ` Jesus Manuel NAVARRO LOPEZ
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=3BBC90C9.309A3D75@ti.com \
--to=cej@ti.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;
as well as URLs for NNTP newsgroup(s).