[SOLVED] Updating slackpkg and add eliloconfig ?

Hello,

after a few times when I forgot to write eliloconfig when upgrade kernel to new one I feel a little bit discriminated against lilo users because slackpkg asked to run lilo. I think it's can be added in function lookkernel() in file post-function.sh of slackpkg to check if /boot/efi is mounted and if is mounted to ask for eliloconfig instead lilo.

It is easy to do this for yourself by adding a custom function to slackpkg. https://www.linuxquestions.org/quest...ml#post5771592

If you know how to create a patch and then send it to Pat Volkerding, the chances of getting it included are higher.

i am also looking for an easier way to set up elilo. At least have the elilo.conf file commented.

But otherwise it seems like elilo is about as simple/complex as it needs to be.
I think I wouldn't want it automated much more than it is.

lilo has simplicity on it's side- there just aren't all that many ways to "do" it,
and only 1 of 2 places to "put" it...

I don't see that same degree of uniformity or simplicity with the array of configurations
possible with elilo

I think it would not be possible to automate it like lilo and still not have a mess of compromises
that nobody's happy with.

Also doesn't hurt to know something about your bootloader on the rare occasions when things go sideways.

.

Originally Posted by solarfields At least have the elilo.conf file commented.

Have a look in /usr/doc/elilo-<version> at README.TXT and elilo.txt.

how i did not think of that

--- /usr/libexec/slackpkg/functions.d/post-functions.sh 2017-10-10 10:40:20.000000000 +0300
+++ post-functions.sh   2018-03-24 10:40:37.865627653 +0200
@@ -212,10 +212,25 @@
                                /sbin/lilo
                        fi
                else
-                       echo -e "\n
+                       if [ -d /sys/firmware/efi ]; then
+                               MACHINE=$(uname -m)
+                               if mount | grep vfat | grep -wq /boot/efi ; then
+                                       if [ "$MACHINE" == "x86_64" ]; then
+                                               cp /boot/elilo-x86_64.efi /boot/efi/EFI/Slackware/elilo.efi
+                                       else
+                                               cp /boot/elilo-ia32.efi /boot/efi/EFI/Slackware/elilo.efi
+                                       fi
+                                       cp /boot/vmlinuz /boot/efi/EFI/Slackware/vmlinuz
+                                       echo -e "\n
+Your kernel image was updated and copied with elilo efi file to /boot/efi/EFI/Slackware.
+Check it out before reboot. If you need start eliloconfig to adjust your boot manager."
+                               fi
+                       else
+                               echo -e "\n
 Your kernel image was updated and lilo is not found on your system.
 You may need to adjust your boot manager (like GRUB) to boot appropriate
 kernel."
+                       fi
                fi
        fi
 }

Here is what I do, now is time to wait for new kernel in current to test the changes. If some one bash guru find error, pls let me know.

@gildbg - Thanks for taking on the challenge!
My minor quibble is that the user should be be prompted to make the changes, rather than accept the changes after they have have been made.

A couple of caveats:
1. For a full install the file /sbin/lilo will exist and the patch will never be run. One solution is to delete the file but a better test would be

if [ -f /etc/lilo.conf ]

as the elilo.conf is only created if lilo is configured.
2. Will not work for generic kernels.

Yep,
it's should be: if [ -x /sbin/lilo ] && [ ! -d /sys/firmware/efi ]; then
I now saw it.

--- /usr/libexec/slackpkg/functions.d/post-functions.sh 2018-03-26 17:02:38.674602360 +0300
+++ post-functions.sh   2018-03-26 17:01:15.206302661 +0300
@@ -203,7 +203,7 @@
 lookkernel() {
        NEWKERNELMD5=$(md5sum /boot/vmlinuz 2>/dev/null)
        if [ "$KERNELMD5" != "$NEWKERNELMD5" ]; then
-               if [ -x /sbin/lilo ]; then
+               if [ -x /sbin/lilo ] && [ ! -d /sys/firmware/efi ]; then
                        echo -e "\n
 Your kernel image was updated.  We highly recommend you run: lilo
 Do you want slackpkg to run lilo now? (Y/n)"
@@ -212,10 +212,25 @@
                                /sbin/lilo
                        fi
                else
-                       echo -e "\n
+                       if [ -d /sys/firmware/efi ]; then
+                               MACHINE=$(uname -m)
+                               if mount | grep vfat | grep -wq /boot/efi ; then
+                                       if [ "$MACHINE" == "x86_64" ]; then
+                                               cp /boot/elilo-x86_64.efi /boot/efi/EFI/Slackware/elilo.efi
+                                       else
+                                               cp /boot/elilo-ia32.efi /boot/efi/EFI/Slackware/elilo.efi
+                                       fi
+                                       cp /boot/vmlinuz /boot/efi/EFI/Slackware/vmlinuz
+                                       echo -e "\n
+Your kernel image was updated and copied with elilo efi file to /boot/efi/EFI/Slackware.
+Check it out before reboot. If you need start eliloconfig to adjust your boot manager."
+                               fi
+                       else
+                               echo -e "\n
 Your kernel image was updated and lilo is not found on your system.
 You may need to adjust your boot manager (like GRUB) to boot appropriate
 kernel."
+                       fi
                fi
        fi
 }

Why do you think will now work for generic kernels ? If the kernel images is different script will copy from boot directory file vmlinuz to /boot/efi/EFI/Slackware/vmlinuz

As far as I understand it the /boot/vmlinuz is a symlink to the huge kernel. Users of the generic kernel would need to copy /boot/vmlinuz-generic. They would also have to update their initrd file. It's a long time since I've used a generic kernel and possibly my memory is playing tricks with me :-(

As an aside to help someone in a remote location to install Slint alongside Debian I recently used grub.

Easy way to upgrade the boot loader after a kernel upgrade, or just when installing it register a new system in the boot manager:

grub-mkconfig -o /boot/grub/grub.cfg
grub-install /dev/sda

Additionally in case of multi boot of Linux systems these commands can be typed from the any of these systems.

It's worked like a charm

@Didier Spaier suggestion trying to resolve the problem when you upgrade your kernel and work on mixed machines few with LILO few with ELILO and and write reboot after upgrade without to copy vmlinuz file to in /boot/efi/EFI/Slackware/ and then you realize that this machine is with ELILO not with LILO and you are ....

@phi11ip I look into slackpkg files and did not see such functionality if you are with LILO. I added initrd check

@allend I added yes or no question for copy new files as you suggest. Also I added error message if efi directory is not mounted.
My english isnt so good, so pls fix the language errors.

--- /usr/libexec/slackpkg/functions.d/post-functions.sh	2018-03-30 16:43:13.825538532 +0300
+++ post-functions.sh	2018-03-30 16:43:05.899623732 +0300
@@ -203,7 +203,7 @@
 lookkernel() {
 	NEWKERNELMD5=$(md5sum /boot/vmlinuz 2>/dev/null)
 	if [ "$KERNELMD5" != "$NEWKERNELMD5" ]; then
-		if [ -x /sbin/lilo ]; then
+		if [ -x /sbin/lilo ] && [ ! -d /sys/firmware/efi ]; then
 			echo -e "\n
 Your kernel image was updated.  We highly recommend you run: lilo
 Do you want slackpkg to run lilo now? (Y/n)"
@@ -212,10 +212,38 @@
 				/sbin/lilo
 			fi
 		else
-			echo -e "\n
+			if [ -d /sys/firmware/efi ]; then
+				MACHINE=$(uname -m)
+				echo -e "\n
+Your kernel image was updated.  We highly recommend you to copy elilo, vmlinuz and initrd
+to /boot/efi/EFI/Slackware/ Do you want slackpkg to do that for you ? (Y/n)"
+				answer
+				if [ "$ANSWER" != "n" ] && [ "$ANSWER" != "N" ]; then
+					if mount | grep vfat | grep -wq /boot/efi ; then
+						if [ "$MACHINE" == "x86_64" ]; then
+							cp /boot/elilo-x86_64.efi /boot/efi/EFI/Slackware/elilo.efi
+						else
+							cp /boot/elilo-ia32.efi /boot/efi/EFI/Slackware/elilo.efi
+						fi
+						cp /boot/vmlinuz /boot/efi/EFI/Slackware/vmlinuz
+						if [ -r /boot/initrd.gz ]; then
+							cp /boot/initrd.gz /boot/efi/EFI/Slackware 1> /dev/null 2> /dev/null
+							touch -r /boot/initrd.gz /boot/efi/EFI/Slackware/initrd.gz
+						fi
+						echo -e "\n
+Your kernel image was updated and copied with elilo efi file and initrd.gz if exists to /boot/efi/EFI/Slackware.
+Check it out before reboot. If you need start eliloconfig to adjust your boot manager."
+					else
+						echo -e "\n
+Your efi partition is not mounted. Check that before reboot."
+					fi
+				fi
+			else
+				echo -e "\n
 Your kernel image was updated and lilo is not found on your system.
 You may need to adjust your boot manager (like GRUB) to boot appropriate
 kernel."
+			fi
 		fi
 	fi
 }