From: NoEMail@home.org   
      
   Henrik Carlqvist  wrote:   
   > On Thu, 07 Dec 2023 06:21:33 +0000, Petri Kaukasoina wrote:   
   >   
   >> root   wrote:   
   >>>After customizing the installation I tried slackpkg upgrade and, with   
   >>>lots of deleting and installing,   
   >>>it produced a system that did not boot. It was as if the kernel did not   
   >>>match the modules.   
   >>   
   >>  "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."   
   >   
   > Yes most likely the boot loader is still loading the old kernel which no   
   > longer has any matching modules installed.   
   >   
   > regards Henrik   
      
      
      
   Thanks Henrik. I plan to try upgrade again when I get to position   
   that I can recover if it fails. In that case, I suppose that   
   slackpkg upgrade   
   will also create a new initrd, and all I will have to do   
   it re-run lilo before booting into the new system?   
      
      
   I have been preparing my systems which are still running   
   14.2 for the time that it will no longer be supported.   
   Several such systems run rtorrent, the latest version   
   of which seems inoperable on 15.0 or current. Slackbuilds   
   has dropped rtorrent/libtorrent, and none of the   
   slpkg mirrors have them either.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)