Kir Kolyshkin 1cdbff1c84 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>

2020-08-03 10:01:03 +02:00

..

00-entry-directory.install

treewide: more portable bash shebangs

2020-03-05 17:27:07 +01:00

50-depmod.install

treewide: more portable bash shebangs

2020-03-05 17:27:07 +01:00

90-loaderentry.install

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

2020-08-03 10:01:03 +02:00

kernel-install

kernel-install: extend --help

2020-06-05 16:34:05 +02:00

meson.build

Add meson build option to prevent building kernel-install

2020-04-14 20:22:32 +02:00