OK, I know just enough about compiling kernels to be dangerous. I have compiled a new kernel for a Slackware installation by following a very simple procedure.

1. Download the kernel source from kernel.org and put it in /usr/src.
2. Unpack the tar ball.
3. CD to the new directory.
4. Make menuconfig - set kernel options.
5. make bzImage
6. make modules
7. make modules_install

(Several steps regarding cp and ln -s have not been shown.)

Everything seems to be working perfectly.

But, when I look at Debian procedures for compiling a new kernel, I am confused.

Must I use a Debian source for a new kernel or can I use one from kernel.org?

If I used a kernel from Debian unstable on a Sarge installation, will something break? (I want a kernel version at least 2.6.11.)

Last, is there a way to use my current kernel configuration and make changes to it in make menuconfig rather than starting all over with a stock configuration?

The sticky thread here uses the "Debian Way" to compile a kernel, apt-get, etc. Why can't I just use the simple method described at the beginning of this post which has worked with no problems on three other distros?

Thanks for any help and insight, jimbo

You can use any kernel. However, you may regress some patches provided by your distribution, which are not in the mainline (kernel.org) kernel. Unstable kernels are (surprise) not as stable, so there may be some breakage. Depending on your specific configuration, it may or may not impact you. Easiest way to find out is to try it (and report problems to where you got the kernel, so bugs can be fixed).

You can use your old config file. Before the "make menuconfig", copy the ".config" to the new kernel's directory, and "make oldconfig". This will apply applicable existing configuration items, and prompt you for new items. You can then "make menuconfig" if needed.

i use the more "slackware"-like method you describe on my debian box, and i've never had a problem (that i could trace to the kernel, at least ). there are probably a zillion reasons i don't know of why that's a bad idea, but as much as i wanted to, i could never get the "debian way" to freaking work. so i just stuck with the "regular" method and it's been okay.