All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Cc: hornber@btconnect.com
Subject: Re: [linux-lvm] Patching my kernel.
Date: 09 May 2001 07:43:14 -0400	[thread overview]
Message-ID: <989408594.3725.3.camel@localhost> (raw)
In-Reply-To: <20010509160319.C898@66bassett.freeserve.co.uk>

On 09 May 2001 16:03:19 +0100, Joe Thornber wrote:
> On Wed, May 09, 2001 at 06:39:31AM -0400, Rupert Heesom wrote:
> > On 09 May 2001 08:51:10 +0200, Luca Berra wrote:
> > > On Tue, May 08, 2001 at 07:11:14PM -0400, Rupert Heesom wrote:
> > 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.
> 
> Just keep a copy of the .config file, when you untar a new kernel
> tree copy the .config file back and do a 'make oldconfig', you will be
> prompted for any new options.
> 
> I tend to have a few of these .config's for different setups.  eg. 
> 
> config-2.2-new_raid-lvm-kdb
> config-2.2-lvm-kdb
> etc.

Joe:  I've untarred a new kernel archive & sorted the linux symlink to
"kernel-2.4.3", etc.  Copied the .config file to the linux directory.

Then ran the patch -p1 < <path to patch file> from the linux directory.

I got a whole lot of errors -

[root@localhost linux]#patch -p1 <
/usr/src/patch_gen_7/PATCHES/lvm-0.9.1_beta7-2.4.3.patch
patching file include/linux/lvm.h
Hunk #1 FAILED at 67.
Hunk #2 FAILED at 75.
Hunk #3 FAILED at 616.
Hunk #4 FAILED at 639.
4 out of 4 hunks FAILED -- saving rejects to file
include/linux/lvm.h.rej
patching file drivers/md/lvm.c
Hunk #1 FAILED at 194.
Hunk #2 FAILED at 359.
Hunk #3 succeeded at 459 with fuzz 2 (offset 11 lines).
Hunk #4 FAILED at 1126.
Hunk #5 FAILED at 1166.
Hunk #6 FAILED at 1204.
Hunk #7 FAILED at 1310.
Hunk #8 FAILED at 1350.
Hunk #9 FAILED at 2314.
8 out of 9 hunks FAILED -- saving rejects to file drivers/md/lvm.c.rej
can't find file to patch@input line 229
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- linux/drivers/md/lvm-fs.c.orig	Wed Apr 11 23:49:20 2001
|+++ linux/drivers/md/lvm-fs.c	Mon May  7 18:40:26 2001
--------------------------
File to patch: 

What am I doing wrong??  I next tried to run the "make oldconfig" from
the linux directory.  It didn't ask for any input, just did it's thing.
Then I reran the patch command, but with the same result.

What a learning curve!!  What next?
-- 
regs
rupert

  reply	other threads:[~2001-05-09 11:43 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
2001-05-09 14:43     ` Patrick Caulfield
2001-05-09 15:03     ` Joe Thornber
2001-05-09 11:43       ` Rupert Heesom [this message]
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=989408594.3725.3.camel@localhost \
    --to=raheesom@navpoint.com \
    --cc=hornber@btconnect.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.