RE: Kernel patch


Subject: RE: Kernel patch
From: Leif Sawyer (lsawyer@gci.com)
Date: Wed Oct 24 2001 - 11:27:59 AKDT


Greg Madden [pabi@gci.net] writes:
> Mike Tibor wrote:
> > When I was tracking the ac patches on my alpha pretty
> > closely, here was my routine:
> >
> > bzcat linux-2.2.x.tar.bz2 | tar xf -
> > mv linux linux-2.2.x
> > cd linux-2.2.x
> > bzcat ../patch-2.2.x-ac12.bz2 | patch -p1
> > [make yadayadayada]
> >
> > Then when a new ac patch came out,
> >
> > cd linux-2.2.x
> > make clean
> > bzcat ../patch-2.2.x-ac12.bz2 | patch -R -p1 # reverses old patch
> > bzcat ../patch-2.2.x-ac13.bz2 | patch -p1
> > [make yadayadayada]
> >

I'm just about this, but I only like to extract and patch once:

bzcat linux-2.2.x.tar.bz2 | tar xf -
cp -la linux linux-2.2.x
cd linux
bzcat ../patch-2.2.x-ac12.bz2 | patch -p1
make ...

then, for each new patch:

mv linux linux-2.2.x-ac12
cp -la linux-2.2.x linux
cd linux
bzcat ../patch-2.2.x-ac13.bz2 | patch -p1
cp ../linux-2.2.x-ac12/.config .
make oldconfig .. ..

Saves on disk space, and i get to keep multiple copies
online (that are easy to clean up as well)

the cp -la only links the files, and patch is smart
enough to unlink before patching, so you only get new
or changed files in each tree.



This archive was generated by hypermail 2a23 : Wed Oct 24 2001 - 11:28:01 AKDT