Despite the last release of LILO being in 2015, it seems that it is
still the default x86 bootloader and wants to be called to "install" the
new kernel image when it has been replaced on the disk. To allow
arch-specific programs like this to be called in future changes, move
the logic to an arch-specific test now.
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
scripts/install.sh | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/scripts/install.sh b/scripts/install.sh
index 92d0d2ade414..2adcb993efa2 100644
--- a/scripts/install.sh
+++ b/scripts/install.sh
@@ -54,10 +54,15 @@ install "$2" "$4"/vmlinuz
install "$3" "$4"/System.map
sync
-if [ -x /sbin/lilo ]; then
- /sbin/lilo
-elif [ -x /etc/lilo/install ]; then
- /etc/lilo/install
-else
- echo "Cannot find LILO."
-fi
+# Some architectures like to call specific bootloader "helper" programs:
+case "${ARCH}" in
+ x86)
+ if [ -x /sbin/lilo ]; then
+ /sbin/lilo
+ elif [ -x /etc/lilo/install ]; then
+ /etc/lilo/install
+ else
+ echo "Cannot find LILO."
+ fi
+ ;;
+esac
--
2.31.1
