On 12/15/22 3:04 PM, Felix Miata wrote:
home user composed on 2022-12-15 14:03 (UTC-0700):
...
installonly_limit= determines how many kernels dnf will keep installed when it is
performing its excess installed kernels removal process. The idea is too allow a
larger safety margin for your working 5.19 kernel before its removal would be
attempted.
If I understand you correctly, this is what allowed me to use the
work-around that you recommended on Nov. 3/4 - using the kernel from
before the Nov. 03 "dnf upgrade" that caused the trouble. Now I know
what controls that. Thank-you.
Alternatively, you could modify /etc/dnf/dnf.conf by entirely excluding kernels
from being installed or removed by dnf:
exclude=" kernel* "
Using this option, dnf will pretend kernels don't exist for purposes of adding or
removing. When you are ready to allow a kernel to be installed, remove the kernel
from the exclude= line. I do that using a one character change in dnf.conf:
exclude=" 0kernel* "
Even when dnf.conf excludes kernels, kernels may still be added or removed using
rpm directly.
Seems like neat tricks. Thank-you. But I hope you understand when I
say that I hope I never need to use them!
_______________________________________________
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
