System.map / Kernel association.
 

After looking up various Google scenarios to find an answer, I seem to not get a specific answer.

I know there needs to be a System.map file and I am under the impression it needs to be associated to the specific kernel being loaded... What confuses me is by default System.map uses the installed kernel but from what I read when recompiling, it mentions to remove "rm System.mal" and then "ln -s System.map-new-kernel System.map (overwriting original?).

My question is, let's say my recompiled kernel is a failure of ignorance, and it doesn't boot, will my original working kernel still boot even though I linked the recompiled kernel/System.map to the standard System.map?

I guess I am asking because I recompiled, got a kernel panic (how original) and when I boot my original I get a plethora of errors and it won't boot. All i did was recompile and modify lilo and added new kernel as well as rm original System.map and overwrite the original.

I never remove my system map files, I just do compile the kernel run make install and everything is great. you dont need to remove the system map symlink, you can but its only for legacy purposes.

Alright so I can skip the "rm System.map" file but what does the new Kernel associate itself with? Maybe I just don't understand how the two work in conjunction. After I recompile the new kernel do I still need to link the new
System.map-new-kernel to System.map.

From what I gather /boot/vmlinuz will look at System.map so /boot/vmlinuz-new-kernel will look for System.map-new-kernel or still System.map?

System.map is used for kernel debug and profiling, not required otherwise.

Cheers