On 19/05/2023 00:21, home user wrote:
> During this afternoon's patching (via dnf), a warning GUI popped up
> saying /boot is full. [...] 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.
The actual grub menu entry is caused by a file in /boot/loader/entries .
If you manually remove the rescue files (initramfs and vmlinuz) but
leave the file in /boot/loader/entries in place, you will still have the
entry in the grub menu but it will not work.
The rescue kernel should automatically be regenerated on the next kernel
update. To prevent that from happening, you also have to remove the
package dracut-config-rescue.
> 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?
The only other "safe" way I can think of to significantly clear up space
on /boot (unless you have some unusual files in there) is to uninstall
old kernels. By default three kernel versions are kept at the same time,
but this could be reduced to two by setting "installonly_limit=2" in
/etc/dnf/dnf.conf
If you want an immediate result but not only on the next kernel update,
you likely have to remove the rpm packages of the oldest kernel manually.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
