My /boot is never mounted, as per default gentoo philosophy. And when it is mounted, it's mounted under /mnt/boot. However, after doing emerge --world update I notice this: -------------------- root@gamma /boot # pwd /boot root@gamma /boot # ls -l total 36 lrwxrwxrwx 1 root root 1 Jan 15 14:31 boot -> . -rw-r--r-- 1 root root 7708 Jan 15 16:42 boot-bmp.b -rw-r--r-- 1 root root 7680 Jan 15 16:42 boot-menu.b -rw-r--r-- 1 root root 5920 Jan 15 16:42 boot-text.b lrwxrwxrwx 1 root root 11 Jan 15 16:42 boot.b -> boot-menu.b -rw-r--r-- 1 root root 728 Jan 15 16:42 chain.b drwxr-xr-x 2 root root 4096 Jan 15 16:40 grub -rw-r--r-- 1 root root 656 Jan 15 16:42 os2_d.b -------------------- If these files were in fact meant to overwrite anything in my real /mnt/boot partition, obviously they didn't succeed, and they created a /boot with stuff in it. Considering that some people might be using /boot as a mount point and have boot partition unmounted at most times, that is not good. The issue is: should boot partition be mounted in /boot prior to emerge --world update? If so, can emerge check to make sure it's mounted prior to executing update? Or, perhaps, only check it if lilo/grub are being updated? Or perhaps it should be mounted under /mnt/boot instead? Should this be documented on gentoo.org or in emerge --world update's output?
This also happened when i did an 'emerge update' on my system.
not sure how to solve this one cleanly.
the to be implemented pkg_prereq() ebuild function could check if /boot is mounted and exit with an error message if it's not
fixed in lilo-22.1-r2 and grub-0.90-r5, additional pkg_setup() function provides the required checks and tries to mount /boot automatically
