From: "Erick Calder" <e@arix.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] rh kernel patches
Date: Tue, 4 Sep 2001 13:14:26 -0700 [thread overview]
Message-ID: <001b01c1357e$3228a340$0300000a@pacbell.net> (raw)
In-Reply-To: <20010904175605.40186.qmail@web13402.mail.yahoo.com>
Pierre,
I'd like to pass on some very useful advice I received from this list.
the LVM patches are made against Linus' kernel (which you can find at
kernel.org). RedHat makes modifications to the kernel (to add device
drivers and god knows what else) and so the LVM patches may or may not work
against the RH-modified kernel, depending on whether RH modified some piece
that LVM patches.
The simplest thing to do is to just get the latest Linus kernel. I
struggled with the RH 2.4.7 kernel until I decided it was not worth the time
and went and got the Linus kernel. Make sure to get the LVM rc1 (at least)
since the 1.0 release had some problems with changes that Linus made.
I'm now happily running RH 7.0 with the 2.4.9 kernel.
- e
-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Pierre Lamb
Sent: Tuesday, September 04, 2001 10:56 AM
To: linux-lvm@sistina.com
Subject: [linux-lvm] rh kernel patches
Is there a correct way to patch RH kernels. I have
tried using the "final path" to update 2.4.7 rh kernel
but just get errors. Is there a work around for this
problem.
next prev parent reply other threads:[~2001-09-04 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 17:56 [linux-lvm] rh kernel patches Pierre Lamb
2001-09-04 18:11 ` svetljo
2001-09-04 19:25 ` Pierre Lamb
2001-09-04 19:43 ` Lewis Bergman
2001-09-04 19:53 ` Joe Thornber
2001-09-04 20:44 ` Pierre Lamb
2001-09-04 23:10 ` svetljo
2001-09-04 19:22 ` Joe Thornber
2001-09-04 20:14 ` Erick Calder [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 5:34 Jean-Eric Cuendet
2001-09-05 19:34 ` svetljo
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='001b01c1357e$3228a340$0300000a@pacbell.net' \
--to=e@arix.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 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.