Maybe my kernel will work - log files

[Aaron Grewell]

Try -p1 instead of -p0.  If that doesn't work, copy the XFS patch into
the linux-2.4.20 directory and patch from there, first with -p0 and then
with -p1.  If that doesn't work, there's a mismatch between the patch
you got and your kernel.

On Mon, 2002-12-30 at 13:17, Bonez wrote:
> Here's how I proceeded: 
> 
> I untarred the source linux-2.4.20.tar.gz within my directory 
> /home/scott/kernel to create linux-2.4.20. Then after copying two patch files 
> for Win4Lin into /linux-2.4.20 (Kernel-Win4Lin3-2.4.20.patch, 
> mki-adapter.patch) I ran the following: patch -p1 < 
> Kernel-Win4Lin3-2.4.20.patch > patch301202.log 2>&1   
> 
> followed by 
> 
> perl -p -i -e "s/^EXTRAVERSION.*/EXTRAVERSION = -mywin4lin/" Makefile 
> 
> (I replace "mywin4lin" in this command with "w4l301202" to signify today as 
> the script day.)
> 
> Then I ran 
> 
> patch -p1 < mki-adapter.patch >mkipatch301202.log 2>&1
> 
> After checking the log files for these and finding no errors (these are 
> attached for review), I proceeded with patching as follows: 
> 
> patch -p0 < xfs-2.4.20-all-i386 > xfspatch301202.log 2>&1
> 
> A reviewe of this log file shows some problems. I do not understand what they 
> mean or how they affect my kernel. The XFS patch was executed from my 
> /home/scott/kernel directory, which per the instructions, is above my 
> /linux-2.4.20 directory. Lonni's suggestion about creation of a symlink 
> evades me, where it's suggested that I "create a symlink, 2.4.20 that points 
> to wherever you put the kernel source". The source in my case resides in 
> /home/scott/kernel/linux-2.4.20.
> 
> Scott
> 
> I am enclosing the .log files generated when patching my kernel with 
> xfs-2.4.20-all-i386. 
> 
> ______________________________________________________________________
> 
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users