commit 3ceaa81c61b654ebf562464d142675bd4d57d7b6
author Kir Kolyshkin <kolyshkin@gmail.com> Fri Jul 31 19:24:15 2020 -0700
committer Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> Sun Sep 20 12:43:58 2020 +0200
tree 97b51554a8d62f0c839892aafbec8a4701b042f9
parent ecbb5a4f6796cbb9d370ab881155ed1b29142c8f

kernel-install/90-loaderentry: fix when /boot is not mountpoint

I happen to have a machine where /boot is not a separate mountpoint,
but rather just a directory under /. After upgrade to recent Fedora,
I found out that grub2 can't find any new kernels.

This happens because loadentry script generates kernel and initrd file
paths relative to /boot, while grub2 expects path to be relative to the
root of filesystem on which they are residing.

This commit fixes this issue by using stat's %m to find the mount point
of a partition holding the images, and using it as a prefix to be
removed from ENTRY_DIR_ABS.

Note that %m for stat requires coreutils 8.6, released in Oct 2010.

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit 1cdbff1c844ce46f1d84d8feeed426ebfd550988)
(cherry picked from commit 2ee1c57c4ff4fd3349cf03c2e89fbd18ca0b3a4a)
(cherry picked from commit 325edff51a8f03c8c777a6c2762e7891266cc9dc)