From: Henrik.Carlqvist@deadspam.com   
      
   On Wed, 08 Mar 2023 15:29:43 +0000, root wrote:   
      
   > Over the years I could not count the number of times that one of my   
   > machines which uses lilo has lost its boot sector.   
      
   Even if the boot sector is OK, the position it points to where the kernel   
   should be might no longer be valid.   
      
   > The machine with the lost boot sector had been running 14.2 for several   
   > years. The owner who lives over 100 miles from me brought the machine to   
   > me. I booted the machine with a liveslak drive. The operational   
   > partition on the drive was sda2. I followed these steps:   
   >   
   > mkdir /sda2   
   >   
   > cp /sda2/boot/vmlinuz /boot   
   >   
   > mount /dev/sda2 /sda2   
   > mount --bind /dev /sda2/dev   
   > /dev/sda2/sbin/lilo -r /sda2   
   > sync   
   > umount /sda2   
   >   
   >   
   > and the affected machine was able to boot.   
      
   I guess that you did mount /sda2 before copying its kernel to /boot?   
   However, I don't see any need to copy the kernel. Simply do:   
      
   mkdir /sda2   
   mount /dev/sda2 /sda2   
   /dev/sda2/sbin/lilo -r /sda2   
      
   > This process could be simplified if liveslak or an install usb could   
   > track slackpkg updates.   
   > If, over time, slackpkg updates the kernel the original install disk   
   > cannot be used to get into the system. Similarly, the liveslak kernel   
   > would not match the kernel on the affected system.   
      
   It does not matter if you choose some rescue media like syslinux, knoppix   
   or the Slackware installation media with a completely different kernel.   
   Lilo does not care if the running kernel differs from the kernel lilo is   
   supposed to boot. You can even write lilo configuration files which allow   
   you to choose between many different kernels.   
      
   > What would you have done apart from switching to grub?   
      
   Your choice of bootloader does not matter. The important thing that   
   matters is the text in the changelog when a new kernel package is   
   released by Slackware:   
      
   -8<--------------------------------------------   
   Be sure to upgrade your initrd after upgrading the kernel packages.   
   If you use lilo to boot your machine, be sure lilo.conf points to the   
   correct kernel and initrd and run lilo as root to update the bootloader.   
   If you use elilo to boot your machine, you should run eliloconfig to copy   
   the kernel and initrd to the EFI System Partition.   
   -8<--------------------------------------------   
      
   You will need to update your bootloader, you can do it the easy way or   
   you can do it the hard way with some friend using a rescue media.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)