From: robin_listas@es.invalid   
      
   On 2022-08-20 20:47, Andrew wrote:   
   > Carlos E.R. wrote:   
   >> On 2022-08-12 20:02, Andrew wrote:   
   >>> The older system has another problem anyway, my /boot partition is   
   >>> over 500MB and has around 50% free with the current kernel and the -1   
   >>> kernel.   This is insufficient when it comes to installing a new   
   >>> kernel and I'm going to have to start getting rid of the -1 kernel   
   >>> before installing the new one.  The beast is dual-boot with Windows   
   >>> 10 and I am not prepared to risk moving the main Windows partion   
   >>> which is just behind /boot.   
   >>   
   >> Try instead uninstalling "plymouth" (and then run mkinitrd).   
   >>   
   >> This package does the graphic display during boot, and it makes the   
   >> kernel image much larger.   
   >>   
   >> 500 M should be enough.   
   >>   
   >> Telcontar:~ # df -h | grep boot   
   >> /dev/nvme0n1p4        1011M   98M  862M  11% /boot   
   >> /dev/nvme0n1p1         500M   19M  482M   4% /boot/efi   
   >> Telcontar:~ #   
   >>   
   >>   
   >   
   > Thanks, that particular machine is a test system so I tried it.  It   
   > still boots with no problems but I won't see if it really helped until   
   > the next kernel comes along.   
   > It's my only pre-UEFI system and has been running since 2010, which is   
   > why the /boot is sized the way it is.   
      
      
   You can simply do:   
      
   df -h /boot   
      
   before and after removing the package, to see the effect it has.   
      
   This is the file that changes:   
      
   cer@Telcontar:~> ls -lh /boot/initrd*   
      
   ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.63-default   
   ... 13M Aug  8 14:45 /boot/initrd-5.3.18-150300.59.87-default   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)