On Thu, Nov 10, 2011 at 09:30:58AM -0500, Brenda J. Butler wrote: > Please let me know if there is any other info you need. I'm not > sure what to do next.
I've gotten the source for the kernel I'm using, and put a bunch of debug statements in the kernel/fork.c:do_fork routine (to distinguish between all the ENOMEM returns) - but I'm not sure how to compile it the Debian way. I'm following instructions from http://kernel-handbook.alioth.debian.org/ch-common-tasks.html: To prepare, I make a fresh new directory: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc Apply patches: /src/kernel-patches/all/2.6.32/apply/debian 5 Make my changes: cd linux-2.6-2.6.32 vi kernel/fork.c Then when I try to compile: fakeroot make -f debian/rules.gen binary-arch_amd64_xen the build system applies the patches from -6 onward (which is bad, I don't want this, but willing to see if the patches will be unapplied in a later step), and failing and halting when it gets to a patch that wants to edit fork.c. I've tried removing the patches involved with -6 forward, but I must have done it badly because now the patches from the beginning through -5 don't apply cleanly. So, I'm trying to figure this out ... any help would be appreciated to get me moving forward more quickly. I'd really like to build a kernel that matches all my modules so I only have to replace the vmlinuz file for this test. bjb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org