On 5/18/23 4:21 PM, home user wrote:
(f37 stand-alone dual-boot workstation)
During this afternoon's patching (via dnf), a warning GUI popped up saying /boot is
full. It offered me the option to move /boot files to trash, but no option to delete
anything. I tried moving the rescue file to trash, but the GUI said it couldn't.
After the dnf patching finished, I removed the rescue file via the rm command. But when I
rebooted, the rescue option was still in the grub menu.
I'm comfortable using rm in regular hard drive areas like /home. But I'm neither
a trained nor a professional sys.admin. I'm seriously uneasy about simply rm-ing
files in /boot. What should I clear out of /boot, and what's the best-practice way?
Please tell me what specific information you need to help me so I can provide it.
thanks,
Bill.
I did my weekly patches this morning. It was the cleanest I've experienced in a few
weeks.
* the grub menu now includes a current rescue kernel.
* there are now 3 regular kernels in the grub menu.
* /boot is 69% used; I saw nothing in it that didn't belong (was too old).
* no more akmods-shutdown.service during shutdown.
One more kernel update is needed to make sure the weekly patches does not keep too many
kernels, and that the rescue kernel is updated.