From: hyperspace.flyover@vogon.gov.invalid   
      
   Carlos E.R. wrote:   
   > On 2023-04-04 17:55, Don Spam's Reckless Son wrote:   
   >   
   >> One last comment on this subject.   
   >> I have a system where /boot is only large enough for two kernels   
   >> (actually, 3 would fit easily but the update process refuses to try)   
   >> so I have to remove the older kernel once I can see that the newer one   
   >> is working fine.  Normally I go there and remove it using yast ->   
   >> software -> software management -> versions.   
   >   
   > You could try to remove "plymouth" package, it is big and goes into   
   > initrd. However, boot will be in text mode.   
   >   
   > It might be enough bytes to make the 3 kernels fit.   
   >   
      
   You made that suggestion several months ago and I tried it, it did not   
   help.  There is easily enough room in /boot for three kernels, it is the   
   update process being anal.  Two kernels take around 50% of /boot so four   
   kernels would probably not work.   
      
   >   
   >> Since the previous installed kernel had been retracted, I decided to   
   >> ssh into the machine and mark the retracted kernel with "-" to   
   >> uninstall it.   
   >> Of course it uninstalled both the old broken-with-intel-graphics   
   >> kernel along with the new one.  Luckily everything I needed was in   
   >> memory and I could simply install the three current "kernel-default*"   
   >> packages again.   
   >>   
   >> We live and learn.   
   >   
   > kernel is a multiversion package. If you tick the top one, it deletes   
   > them all. You have to do it in the "version" tab in yast.   
   >   
      
   Yes, I saw that.  I had thought I was just removing the Retracted   
   Installed Packages but when it listed the six packages it had removed it   
   was obvious that I had no kernel left.   
   Using the Version tab is what I normally do.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)