The biggest stumbling block is achieving internet network connectivity with Network adapter Module.
The symbols table helps developers understand the meaning of a kernel error message; without it, kernel “oopses” (an “oops” is the kernel equivalent of a segmentation fault for user-space programs, in other words messages generated following an invalid pointer dereference) only contain numeric memory addresses, which is useless information without the table mapping these addresses to symbols and function names.
The modules are installed in the The package's configuration scripts automatically generate an initrd image, which is a mini-system designed to be loaded in memory (hence the name, which stands for “init ramdisk”) by the bootloader, and used by the Linux kernel solely for loading the modules needed to access the devices containing the complete Debian system (for example, the driver for SATA disks).
Finally, the post-installation scripts update the symbolic links The configuration steps described in this chapter are basic and can lead both to a server system or a workstation, and it can be massively duplicated in semi-automated ways.
It's a good idea to have at least one extra kernel version installed, because it can happen that your current kernel can get updated and an issue occurs. But "All other kernels basically being RC" is a bit off though - The non-LTS (stable) are debugged ... Any kernel not considered LTS (like 3.19) will simply cease to benefit from further development, security backports, etc. So then you end up with [dead] [LTS] [stable] [rc] complex.
If you then have an extra kernel, then you have a kernel to fall back on. And the RC/non LTS = not suggested for use - is still pretty on point. More reading here : https:// then theres linux-next . The answer to this question really depends on your skill-level.