>>>make mrproper
>>
>>You only need to make mrproper if you apply a patch. Otherwise, it just resets all of your options, which you may not want to do when recompiling the same kernel to get support for an additional device, etc.
>
>Which is probably true if he is building a kernel for the first time...?

If you are doing it the first time from a fresh kernel source the defaults are already selected. =)

>>You should acutally use dd instead of cp.
>
>Curious. Why is that? You're the first I've read who recommends using dd when copying the new kernel to /boot. Have something to do with binary copying?

Well, I guess I don't have a good reason for that. I was always taught to copy it that way. I guess it is a safer way to copy it, but, umm... well.. err.. I ... uhh... Yeah.

>Questions for you Jaason:
>The System.map: a new one is created every time the kernel is compiled and the kernel how to says to copy the System.map to /boot. The System.map is created by compiling the kernel. However, I haven't found a way where you can specify a particular System.map in lilo.conf.

You can't. It always looks for /boot/System.map. That's why I create symbolic links.

> And, if you keep your old kernel around to boot in an emergency how does the new system map satisfy the old kernel?

You'll probably get a bunch of wacky errors, but at least it boots (in an emergency, who cares =)). Or if you want to go back to an old kernel for some reason or another, it's there.

> And if it does why is a new one necessary?

So that you don't always get those errors on boot.

j