grub-094-r1.ebuild seems to wreck the symlink between /boot/grub/menu.lst and /boot/grub/grub.conf The initial / is missing from the symlink, leaving it pointing at a non-existent file. When the system is rebooted you simply get the grub> prompt as grub cannot find the menu. Reproducible: Always Steps to Reproduce: 1. emerge =grub-0.94-r1 2. reboot 3. Actual Results: see above Expected Results: grub menu I thought it was just a foobar by me, but have seen the same problem described in the mailing list.
As I pointed out in Bug #31145, Comment #17, that symlink is bad design and should be eliminated: - Grub looks for its menu in menu.lst, and instead of just using this as the menu file, gentoo insists that this file should instead be maintained as grub.conf, with a symlink from menu.lst so that grub finds it. Thus, gentoo's grub configuration differs from all other operating systems and Linux distributions that use grub, for no discernible reason. - The grub installation becomes dependent on symlinks, which are not available on all file system types. Hence gentoo cannot install grub on file system types such as vfat (Bug #31145).
grub-0.95 fixes this behaviour by reverting to using grub.conf by default, and moves menu.lst to grub.conf if you have only menu.lst in /boot/grub. Adding bug #55732 as a dependency, where an ebuild and patch are provided.
Fixed in grub-0.94-r2. More patches will be added to -r2 as time goes on; these will be added sequentially to allow sufficient testing of each on. This is the first.
