hallo
I usallay run vanilla kernels and build them with a suffix "_MY" to save some
works when cleaning /boot if that kernels gets outdated and a new one gets installed.
/boot looks like this
ll /boot :
...
-rw-------. 1 root root 20M 22. Jun 15:04 initramfs-5.1.14_MY.img
-rw-r--r--. 1 root root 4,7M 22. Jun 15:04 System.map-5.1.14_MY
-rw-r--r--. 1 root root 15M 22. Jun 15:04 vmlinuz-5.1.14_MY
...
and
ll /boot/loader/ :
drwx------. 2 root root 4,0K 22. Jun 15:04 entries
and
sudo ls -l /boot/loader/entries/ :
-rw-r--r--. 1 root root 242 22. Jun 15:04 0637b2e09df64d90bd0c13dc10d1da70-5.1.14_MY.conf
to clean /boot a use a script:
#!/bin/bash
set -vx;
sudo rm -rf /boot/loader/entries/*MY*;
sudo rm -rf /boot/*MY* /lib/modules/*MY*;
sudo grub2-mkconfig -o /boot/grub2/grub.cfg;
and now my problem:
the first sudo rm -rfv command does NOTHING, means the loader entry is still there and I
need to rm it by hand.
whereas the second rm command does what I espect.
What I'm doing wrong / where is the/my bug ?