GRUB portage installs the directory /boot/boot/grub, instead it should /boot/boot should be link to /boot itself. Reproducible: Always Steps to Reproduce: 1. Unmerge GRUB 2. Remove /boot/boot 3. Emerge GRUB 4. Reboot Actual Results: Grub prompt shows up after reboot. Expected Results: Show grub splash, and boot kernel. Verified on GRUB portages version 0.94-r1, 0.94-r2 and 0.95.20040823.
Thanks very much! I think that one might resolve a multitude of headaches. Lots of people seem to remove that symlink thinking it doesn't really matter. Now I know why someone put it there in the first place... :-S I'll investigate further this evening and tomorrow and post back when I know more. Thanks again.
/boot/boot should always exist as a symlink to '.' it makes user's lives easier ... if you always use '/boot/kernel' notation, then it'll work if /boot/ is on the / partition or sep
Agreed... but what if your boot partition is a crappy filesystem such as FAT that doesn't support symlinks? I know of one user who uses that (although I don't know why he does).
Okay, having thought about it, it's your machine that's wrong, not grub. Your grub.conf is wrong. The contents of grub that go into boot: /boot/grub /boot/grub/splash.xpm.gz /boot/grub/grub.conf.sample That's it. The ebuild copies some more stuff across in pkg_postinst: einfo "Copying files from /usr/lib/grub to /boot" cp -p /usr/lib/grub/* /boot/grub cp -p /lib/grub/*/* /boot/grub [ -e /boot/grub/grub.conf ] \ && /sbin/grub \ --batch \ --device-map=/boot/grub/device.map \ < /boot/grub/grub.conf > /dev/null 2>&1 So as such, the only reason anything can possibly be going wrong is that you're incorrectly using the "/boot/kernel" notation in /boot/grub/grub.conf. Closing as INVALID.
