On Thu, Feb 27, 2003 at 10:55:32AM +0000, Gedi wrote: : > From: Mark Hounschell <dmarkh@cfl.rr.com> [snip snip] : > Try patch -p1 <acpi-20021212-2.4.20.diff : : -p1 does not work either. : : I think it revolves around the fact the the patch file looks for : a/arch/i386/config.in or b/arch/i386/config.in. Inconsequential. Please read the man page for patch(1). You'll see that the '-p1' option will strip off the first part of the path in the patch files. : Both the 'a' and 'b' do not exist in the SuSE file hierarchy and this : is what is causing confusion from my side. This is b/c on the machine where the patch was generated, the files were located in /a/... and /b/.... Using '-p1' will negate this issue. : The patch must be correct because these patches are heavily relied : upon and the problem would have been highlighted immediately. The patch is correct. But it's also meant to be applied to a stock linux kernel. Did you grab the linux-2.4.20.tar.tz tarball from kernel.org? Or are you attempting to modify the kernel source for your particular version of SuSE? If it's the first, then you're doing something funky, but we can figure it out and get you on the right path. If it's the second, you may be out of luck. Keep in mind that most vendor kernels have various patches already applied, and thus a patchfile which expects to be applied to the vanilla kernel will most likely fail. --Jerry ps-In the future, please try wrapping your text somewhere around the 70-72 column mark for the sake of readibility. Open-Source software isn't a matter of life or death... ...It's much more important than that!