Since /etc/init.d/modules is executed before /etc/init.d/localmount, modules-update cannot find System.map if /boot and /usr/src/linux are both separate partitions. OK, the user can copy System.map to / or to the unmounted /boot, but this is easily forgotten to do after a kernel upgrade and, moreover, it means a waste of space just because the startup process is "too stupid". The main problem is that /etc/init.d/checkfs depends on "modules". I suggest to make this dependence somehow optional. If one could disable this dependency, then the user could create an /etc/runlevels/boot/.critical with the content checkroot checkfs and then he could write an initscript with dependencies "need checkfs; before modules" which e.g. calls mount -at ext2 (or whatever is reasonable to mount e.g. the /boot partition). Also this solution is not very nice, because "modules" (and thus all subsequent CRITICAL_SERVICES) must be omitted from .critical (because checkroot and modules are treated separately before all other content of .critical and thus before the above script), but at least it works... OK, I know that the user can just hack up /etc/init.d/checkfs to drop the dependency on modules and then use the above trick, but on the next baselayout upgrade he has to remember that. So a more flexible solution would be better. I am not the only user who has /boot and /usr/src/linux on separate partitions (actually, this topic came up in the German forum not by me).
*** This bug has been marked as a duplicate of bug 165134 ***
