Re: [PLUG] kernel patching

[Bill Jonas <bill@billjonas.com>]

On Mon, Apr 29, 2002 at 12:53:52PM -0400, Paul wrote:
> I guess I would just remove the "b" from "bzcat" since I downloaded
> the "gz" files.  So, this command will go through every patch on it's
> own?  That would be very convenient, but is there any good reason to
> do each patch separately?

You could, if you want.  If you'd prefer to do it that way, just use a
little for loop:

$ for file in ../patch-2.4.1*; do zcat $file |patch -p1 -s; done
  # or bzcat, as appropriate

If you were patching from, say, 2.4.0, you'd need to use your wildcards
a bit differently, since the version numbers aren't zero-padded, and
therefore don't properly sort numerically:

$ bzcat ../patch-2.4.[1-9] ../patch-2.4.1[0-9] |patch -p1 -s

(Or the for loop above, if you prefer.)

> Has anyone tried the preemptive kernel patch?

I have.  I like it.  Keep in mind you'll need to reverse the patch
before applying another Linus patch.  Use the -R (or --reverse) option.
One thing you might want to consider is to use the EXTRAVERSION in the
top-level Makefile to keep track of which patches and versions you've
applied:

$ head -4 /usr/local/src/linux-2.4.17/Makefile 
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 17
EXTRAVERSION = preempt1

This was from, for example, the preempt-kernel-rml-2.4.17-1.patch patch
(on my system).

-- 
Bill Jonas    *    bill@billjonas.com    *    http://www.billjonas.com/
"They that can give up  essential  liberty to obtain a little temporary
safety deserve neither liberty nor safety."        -- Benjamin Franklin

Attachment: pgphI0s1Qcd1s.pgp
Description: PGP signature