[lug] Using dnf to Control Fedora Kernel Upgrade Cycle

Maxwell Spangler maxlists at maxwellspangler.com
Thu Nov 26 10:41:16 MST 2015

Modify /etc/dnf/dnf.conf and change installonly_limit to something
larger, or 0 to disable removing old kernels.
On Wed, 2015-11-25 at 22:07 +0000, stimits at comcast.net wrote:
> It looks like Fedora follows a pattern with its kernel upgrades
> whereby up to three old kernels pushed down the stack of grub boot
> options each time a new kernel is installed...so there seems to
> always be the newest kernel plus the prior three. The most recent
> kernel has these rpm packages:
> kernel-4.2.6-300.fc23.x86_64
> kernel-core-4.2.6-300.fc23.x86_64
> kernel-devel-4.2.6-300.fc23.x86_64
> kernel-modules-4.2.6-300.fc23.x86_64
> kernel-modules-extra-4.2.6-300.fc23.x86_64
> However, I've had problems with this newest 4.2.6-300 kernel version,
> while all of the prior versions worked great. If I wanted to make
> sure the slightly older 4.2.5-300 is always left in place, regardless
> of how many future kernel upgrades there are (including grub menu),
> would I be able to do this with a dnf config file?
> For 4.2.6-300, which does not work, blacklisting modules is
> easy...but I really want to blacklist all of the 4.2.6-300 rpm
> upgrades...is this also something which dnf can be configured for
> without a lot of issues?
> Thanks!
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667
> channel=#hackingsociety
Maxwell Spangler
Boulder, Colorado, USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20151126/74e39539/attachment.html>

More information about the LUG mailing list