2016-11-24 1:42 GMT+01:00, Jon LaBadie <jonfu@xxxxxxxxxx>: > On Wed, Nov 23, 2016 at 10:25:30PM +0100, Andras Simon wrote: >> 2016-11-23 21:30 GMT+01:00, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>: >> > On Wed, Nov 23, 2016 at 09:20:23PM +0100, Andras Simon wrote: >> >> The same: it wants to remove that old kernel. But after booting again >> >> the latest kernel and starting the upgrade, dnf wanted to erase the >> >> old kernel, not the newest, running one. So I let it. >> >> Now I'm sitting here with fingers crossed... >> > >> > Keep in mind that it's gonna reboot to do the actual package >> > installation anyway. >> >> Right, so I was wrong: letting dnf remove the only working f23 kernel >> wouldn't have been risky; it would've led to disaster. >> >> Thanks for pointing this out! > > What about temporarily increasing the number of retained kernels. > I think the parameter is in /etc/dnf/dnf.conf, "installonly_limit=3". > > Raise it to say 6 so it will not deleted the currently running kernel. > Later return it to default 3 or whatever you want. It's too late now because the upgrade has already succeded (though I may run into these issues again when I go to F25 or upgrade other laptops) but this problem came up even when I had only one kernel installed with installonly_limit=3. Andras _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx