Created attachment 358218 [details, diff] Docs patch I'm making one last configuration change before this package goes stable and I have to stop messing with it. grub2-install from >=sys-boot/grub-2.00_p5107-r1 will install files in /boot/grub rather than /boot/grub2. This is upstream's default location, and there isn't really a good reason to change it. See attached patch for the handbook and grub2 migration guide.
Sorry for the late action; I notice the ebuild displays the change if the user already had a previous grub2 installed. If a user misses it, am I right in my assumption that the user, when running "grub2-mkconfig -o /boot/grub2/grub.cfg", will not notice anything (errors of any kind) until he ran grub2-install (as it replaces the "old" GRUB2 with the new GRUB2)? Will grub2-install complain about /boot/grub2 still being available while not being used anymore?
(In reply to Sven Vermeulen from comment #1) > If a user misses it, am I right in my assumption that the user, when running > "grub2-mkconfig -o /boot/grub2/grub.cfg", will not notice anything (errors > of any kind) until he ran grub2-install (as it replaces the "old" GRUB2 with > the new GRUB2)? > Correct. Running grub2-install will update the MBR (or EFI binary) with the new path, which means grub will then start looking for /boot/grub/grub.cfg instead of /boot/grub2/grub.cfg. If the user never runs grub2-install, the old version of grub will continue to load /boot/grub2/grub.cfg. > Will grub2-install complain about /boot/grub2 still being available while > not being used anymore? grub2-install does not issue any kind of warning message in this scenario. I thought about adding some migration code to pkg_postinst that would move /boot/grub2 to /boot/grub and create a symlink from /boot/grub2 -> /boot/grub. However, that is a bit tricky: - If /boot is a FAT filesystem, we can't use a symlink. This is common in EFI setups. - We would need to check for conflicting files in /boot/grub.
Ok, I've committed the changes. I hope we don't get (m)any reports about users that ran grub2-install and then still used grub2-mkconfig -o /boot/grub2/grub.cfg and then finding out GRUB2 doesn't load the new kernels. But then again, I'm not sure how many users would run grub2-install after they already switched to grub2...
Hi, I'm User Zero, ... maybe. I updated to grub-2.00_p5107-r1 today ( because the previous version of ~ I had unmasked vanished ). Ran grub2-install to update my mbr, nothing seemed out of place. Ran my automated script that calls grub2-mkconfig, nothing seemed out of place. Rebooted ... OH Dear. This bug is the best that matches my problem, or should I file a separate one? Fortunately I worked out how to load the grub2 config manually and get my system booting again. Only after booting and checking the mtimes in /boot/grub/ did I observe changes had transpired there.
(In reply to Kent Fredric from comment #4) > This bug is the best that matches my problem, or should I file a separate > one? > This is not the place to discuss it. File a new bug if you must.
+ 21 Sep 2013; Mike Gilbert <floppym@gentoo.org> grub-2.00_p5107-r1.ebuild, + grub-9999.ebuild: + Make a symlink from /boot/grub/grub.cfg to /boot/grub2/grub.cfg in case people + don't read the warning.
