LinuxQuestions.org - Any reason to change symbolic links in /boot with generic kernel?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Any reason to change symbolic links in /boot with generic kernel? (https://www.linuxquestions.org/questions/slackware-14/any-reason-to-change-symbolic-links-in-boot-with-generic-kernel-752647/)

Any reason to change symbolic links in /boot with generic kernel?

I have always wondered if I should be changing the System.map and config symbolic links in /boot to point to their respective generic kernel System.map and config when using the generic kernel.

Any documentation I've read about creating an initrd to run the generic kernel never mentions this point, so I assume it is not necessary. I just add the new entry to lilo as below and carry on, leaving the symbolic links pointing to the huge System.map and config. Am I missing anything?

# Start generic kernel
image = /boot/vmlinuz-generic-smp-2.6.29.6-smp
initrd = /boot/initrd.gz
root = /dev/hde2
label = generic
append = "acpi=force"
read-only
# End generic kernel

Thanks

That's fine ... no need to change symlinks for System.map or config.