From: kutcha@eos.acm.rpi.edu (Phillip Rzewski) Subject: Problems patching kernel Date: Mon, 30 Nov 1992 01:28:37 GMT
In the past I have always been one of those people that got the fully
packaged tar.Z of the latest kernel sources and compiled them as a big set.
I never got the patches and applied them to what I had.
Now I have the need to go back and look at some old kernel sources and I
am having major problems with the patching mechanism. I am working with the
files in pub/linux/sources/system on tsx-11.mit.edu. First I got the tar.Z
of the 0.98 sources, and the patches 1, 2, and 3. (I am going for 0.98.3
here).
I have noticed this problem whenever I try to patch kernel sources.
Even" when there is total success, it dumps tons of files into the directory
where I am (/usr/src in this case) when it should have put them somewhere
in the linux directory. I find that by looking through the patch file to see
where they should have gone and moving them manually I can solve the
problem. This didn't bother me when doing the first patch, but when doing the
second patch which contains all the FPU-emu code, it didn't even make the
FPU-emu directory and dumped ALL the FPU files into /usr/src. I even took
the time to move THOSE (plus several other non-FPUs it dumped) to their
homes. Then when doing the third I got a couple failed hunks in Makefile,
a few more dumped files which I moved to their homes. Unfortunately the
failed hunks in the Makefile wrecked everything and now the Makefile is
not useful enough to compile with.
Am I missing an option or something? I read the patch manpage and all
the READMEs in the pub/linux/sources/system directory and nowhere does it
say I should EXPECT this behavior, nor does it suggest a patch command to
use, so I could only assume that if I used "patch -s < patchfile" and
didn't get any complaints it was behaving itself.
Anyone wanna help me out? Is it possible no one else has noticed this
just because they never look at old kernels? :)