After compiling the kernel, Code listing 19.6 directs the user to: cp /usr/src/linux/vmlinux /boot Then, when configuring /etc/silo.conf (or /boot/silo.conf) in Code listing 28.2, the user is directed to include the following line in silo.conf: image = /boot/vmlinux-2.4.21 While experienced users will immediately recognize the naming inconsistency, newer users might not, resulting in confusion. My recommendation would be to modify Code listing 19.6 to read: # cp /usr/src/linux/vmlinux /boot/vmlinux-2.4.21 # ln -s /boot/vmlinux /boot/vmlinux-2.4.21 and also Code listing 28.2 to read, in part: image = /boot/vmlinux Obviously, reasonable minds may differ as to the proper solution, but as it currently stands, a noob following the directions literally will end up with a non-booting system. Reproducible: Always Steps to Reproduce: Actual Results: I never performed the steps as listed in the document, but I would expect them to cause SILO to halt at boot time, failing to locate the kernel image /boot/vmlinux-2.4.21, which is actually named /boot/vmlinux. Expected Results: SILO should be able to locate the kernel image by being pointed, either directly or through a symlink, to it.
Oh, and I guess since the kernel version is now 2.4.22, all of the above should be adjusted accordingly... :^)
Created attachment 21197 [details, diff] Patch to gentoo-sparc-install.xml I took the other way around and used /boot/vmlinux :) The handbook doesn't have this problem. If a docdev can review?
Committed (sorry, no review, but I don't think it was really needed -- no real technical update :)
