[lug] Using dnf to Control Fedora Kernel Upgrade Cycle

Kevin Fenzi kevin at scrye.com
Thu Nov 26 11:53:19 MST 2015

On Wed, 25 Nov 2015 22:07:56 +0000 (UTC)
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. 

Yeah, which you can increase by changing the 
installonly_limit= in /etc/dnf.conf if you like. 

> 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!

There's not really any way I know of to get it to never touch the one
specific kernel, but it won't remove the currently running one I don't
think, so as long as you are booted in it it should leave it alone. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20151126/cb86d197/attachment.pgp>

More information about the LUG mailing list