Is it normal that Fedora's yum list kernel-* shows two versions of kernel being used?

fedora kernel package-management yum

5,474

Solution 1

Yum is not showing the running kernel(s)... You cannot have multiple kernels running simultaneously in a single userspace.

Yum is showing you the installed kernels. Most likely, you are running the 3.6.10 kernel, although checking on it is as simple as running uname -a.

The additional lines are supplementary packages which add additional capabilities to the system. For example, the kernel -devel package is the entire kernel source. This allows you to rebuild the kernel or to build a custom module against that kernel.

Solution 2

Fedora tries to keep several kernels around (by default 3), in case some boot fails horribly and you have to go back to an older one.

5,474

nonopolarity

I started with Apple Basic and 6502 machine code and Assembly, then went onto Fortran, Pascal, C, Lisp (Scheme), microcode, Perl, Java, JavaScript, Python, Ruby, PHP, and Objective-C. Originally, I was going to go with an Atari... but it was a big expense for my family... and after months of me nagging, my dad agreed to buy an Apple ][. At that time, the Pineapple was also available. The few months in childhood seem to last forever. A few months nowadays seem to pass like days. Those days, a computer had 16kb or 48kb of RAM. Today, the computer has 16GB. So it is in fact a million times. If you know what D5 AA 96 means, we belong to the same era.

Updated on September 18, 2022

Comments

nonopolarity almost 2 years
Is it true that the following shows that two versions of the kernel are being used? (Is the bold face -- the one enclosed in ** showing what is currently loaded / used). Basically, I just created a VM using VMWare Fusion on a Macbook Pro, downloaded Fedora (the current one, which is 17), installed it and did the upgrade it prompted me to do in a window.

(The ones I see are kernel.x86_64 3.3.4-5.fc17 and kernel.x86_64 3.6.10-2.fc17, so 3.3.4 and 3.6.10 are both running? How come the other kernel parts like headers, modules, or tools don't need to be running?)
```
$ yum list kernel-*
Loaded plugins: langpacks, presto, refresh-packagekit
(1/2): fedora/primary_db                                 |  14 MB     00:13     
(2/2): updates/primary_db                                | 7.3 MB     00:06     
Installed Packages
**kernel.x86_64**                       3.3.4-5.fc17    @koji-override-0/$releasever
**kernel.x86_64**                       3.6.10-2.fc17   @updates                    
Available Packages
kernel-debug.x86_64                 3.6.10-2.fc17   updates                     
kernel-debug-devel.x86_64           3.6.10-2.fc17   updates                     
kernel-debug-modules-extra.x86_64   3.6.10-2.fc17   updates                     
kernel-devel.x86_64                 3.6.10-2.fc17   updates                     
kernel-doc.noarch                   3.6.10-2.fc17   updates                     
kernel-headers.x86_64               3.6.10-2.fc17   updates   
kernel-modules-extra.x86_64         3.6.10-2.fc17   updates                     
kernel-tools.i686                   3.3.4-5.fc17    fedora                      
kernel-tools.x86_64                 3.6.10-2.fc17   updates 

  [...]
```
- Deer Hunter over 11 years
  
  Yes, you have two kernels installed. For future reference, this may come in useful if after an update you find bugs under the newer kernel. Then you can select the older one manually (e.g. in GRUB you have to press a key - say, Shift, during machine bootup to get the menu to choose the kernel from). It is always a good practice to keep at least two (sometimes three, if you don't spot the bug right away) kernel versions handy.
- Rob Gibson over 11 years
  
  I usually try to keep three. 1. The kernel the distribution was installed with. 2. The most recent known working kernel. 3. The updated version being tested and run. When a new #3 is released and the existing #3 kernel has been working properly, I will remove #2 and the existing #3 becomes the #2 kernel.