In "Code Listing 12: Installing the kernel", the example shows to copy the system map to the /boot directory. No explanation is given. IMHO, this line should either be moved to the "Code Listing 13: Backing up your kernel configuration" section subsequent, or some explanation given as to what the system map is and why it should be copied to /boot. The current placement of this command without explanation makes it seem like this is a critical step, however it does not explain the naming convention to use for the file. For a new user (such as myself) this creates confusion as to what to do with that file when compiling a second version of the kernel. Reproducible: Always Steps to Reproduce:
The role of the System.map file is not important for users to understand, yet it is important for the system to have one. See http://www.dirac.org/linux/system.map/ We don't really have to copy over the System.map file if we don't use several kernels (i.e. once upgraded, we keep using the new kernel). To avoid errors with users who do use several kernels we ask them to copy the file over (with version information) so that the kernel used always uses it's own System.map file. Explaining System.map isn't the goal of our document and it doesn't add real value to the user - it's not vital for the understanding of a Gentoo Linux system. If you disagree, try formulating a short explanation on System.map (read: a few lines at most) that doesn't create more confusion.
FWIW I never ever copy this system.map file. Can it be used from an unmounted /boot partition anyway?
