Follow-up Comment #1, bug #26924 (project grub):
This patch only works by pure chance. Turns out, the core.img you had in
/boot/grub/ was identical to the one you're installing to your target
(designated by --root-directory=).
There's no "right way" to use /boot/grub/core.img for the consistency check,
it's simply the wrong one.
As for using the right one, this would involve a few ugly kludges, since we
need grub-install to tell grub-setup about:
a) the GRUB drive in which is is hosted
b) its relative path
and then, if the desired GRUB drive doesn't match with the drive we're
installing boot.img to, we need to fallback to UUIDs, which is handled in
grub-install anyway.
Considering that this whole mess is only for the sake of supporting
blocklists, which are DEPRECATED, I think the best option is to print a nice
error and abort.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?26924>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-grub
