From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Patching my kernel.
Date: 09 May 2001 06:39:31 -0400 [thread overview]
Message-ID: <989404772.3725.0.camel@localhost> (raw)
In-Reply-To: <20010509085110.G23157@colombina.comedia.it>
On 09 May 2001 08:51:10 +0200, Luca Berra wrote:
> On Tue, May 08, 2001 at 07:11:14PM -0400, Rupert Heesom wrote:
> > I had previously patched the kernel (stock 2.4.3) with the beta 6 patch.
> >
> > Now I'm trying to update to beta 7. I tried patching the kernel is
> > exactly the same way as before (maybe a mistake). Most of the output is
> > pasted in here (at the end). I'm concerned about the prompts I got -
> >
> > "Reversed (or previously applied) patch detected! Assume -R? [n]"
> are you starting with a clean kernel or with the kernel you previously
> patched with b6?
> the former is the correvt approach,
> the latter....
I was not using a clean kernel. I'll try that.
BTW, I know there's a way to keep the config from the "used kernel", so
that I don't have to guess the settings again for my system (I made
several config errors last time). Can you remind me how to migrate the
.config file across to a new source tree? I'll try & find some docs on
how to do this, but have forgotten where I last read about it.
--
regs
rupert
next prev parent reply other threads:[~2001-05-09 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 23:11 [linux-lvm] Patching my kernel Rupert Heesom
2001-05-09 6:51 ` Luca Berra
2001-05-09 8:29 ` Joe Thornber
2001-05-09 10:39 ` Rupert Heesom [this message]
2001-05-09 14:43 ` Patrick Caulfield
2001-05-09 15:03 ` Joe Thornber
2001-05-09 11:43 ` Rupert Heesom
2001-05-09 18:58 ` Joe Thornber
2001-05-10 22:48 ` Rupert Heesom
2001-05-09 11:55 ` David Vidal Rodriguez
2001-05-09 13:11 ` Joe Thornber
2001-05-09 14:21 ` David Vidal Rodriguez
2001-05-09 17:29 ` Luca Berra
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=989404772.3725.0.camel@localhost \
--to=raheesom@navpoint.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