According to Mario Melendez: While burning my CPU.
>
> Richard Adams wrote:
>
> > > I've got patches 2.0.32 --> 2.0.35 for my 2.0.31 box...they are .gz
>
> > > stuff, which I've named /downloads...My understanding of the procedure
> > > to patch the kernel is to run each patch in sequence until it is
> > > 2.0.35...how do I do this correctly? put the unzipped patches in the
>
> > Basicly yes, no need to unzip them tho' see below.
>
> I had a 2.0.33 kernel and upgraded it to 2.0.35 directly without going
> through 2.0.34... so far I've had no problems with my new kernel... is
> the same possible when you upgrade from a kernel < 2.0.33 to 2.0.35?
Do you mean you jumped a patch.?
Patches are made as follows.
A hacker is using a 2.0.33 kernel and makes a lot of code changes which are
then sent to Alan Cox who coordinates the whole show. Alan has a clean
2.0.33 and makes all the changes to the new kernel, he now uses "diff" to
create patches against his CLEAN 2.0.33 kernel, the patch is then called
patch-2.0.34.gz and is used by you and me to patch against a "clean"
2.0.33 kernel which results in our new 2.0.34 kernel, now if you jump a
version like you say, then you have been very lucky that you could even
compile the new source.
I said Alan Cox, but realy Linus Torvalds has the last say before a new
kernel version comes out.
Now if i have understood you correctly you jumped a patch right,??, now do
the following and i think you will see how messed up your source code now
is.
'find /usr/src/linux/ -name *.rej'
I think you will find plenty of them..
Or did i completly misunderstand you.?
>
> --
> //\/\ario //\/\elendez- TI2DLL
> ICQ #6160213
> [EMAIL PROTECTED]
> http://radioplaneta.base.org
>
>
--
Regards Richard.
[EMAIL PROTECTED]
