yum list all available kernels upgrades and not just latest

[ilan.sch]

I have CentOS 7 machine that is running kernel 3.10.0-123.el7.
When i search for new kernels available to download i get:

the command i execute: yum list --showduplicates kernel //command i execute
the output:

Installed Packages
kernel.x86_64 3.10.0-123.el7 @anaconda
Available Packages
kernel.x86_64 3.10.0-693.el7 base
kernel.x86_64 3.10.0-693.1.1.el7 updates
kernel.x86_64 3.10.0-693.2.1.el7 updates
kernel.x86_64 3.10.0-693.2.2.el7 updates
kernel.x86_64 3.10.0-693.5.2.el7 updates
I know there are additional kernel versions that are available, e.g: 3.10.0-229, 3.10.0-327..
How can i display them ? 693 is latest, but i want all.
Do i need to add repositories to yum ? Can i add these respositories automatically ?

Thanks


After adding repositories, i can get all kernels, 229, 327 etc.. but i had to create my own CentOS.repo with baseurls like baseurl=http://vault.centos.org/7.0.1406/os/Source/...

is there a way to avoid manually adding the repos ? cant i configure yum to use all centos available repos ?

[avij]

/etc/yum.repos.d/CentOS-Vault.repo has the repository configurations for the older CentOS releases.

[TrevorH]

All kernel versions except the latest one have security vulnerabilities and should not be used. Most especially you need to update 3.10.0-123 sooner rather than later as it's over 3 years old and has many severe problems.

[jlehtone]

i want all.

... and you want it now. Don't we all?

However, wanton desires are seldom good for us, as Trevor did point out. Some even believe that they need -- a stronger form of want.

Not using the latest kernel is an abomination.


That said, yum does have:

Code: Select all

yum repolist

and

Code: Select all

yum repolist all

yum does have the --enablerepo= option to temporarily enable a repo.

There is also

Code: Select all

yum-config-manager --enable <reponame>

but the less you have permanently enabled repos, the better.

[ilan.sch]

Hi, /etc/yum.repos.d/CentOS-Vault.repo is empty..
[root@CentOS70 ilan]# cat /etc/yum.repos.d/CentOS-Vault.repo
# placeholder for now
# #
# CentOS Vault contains rpms from older releases in the CentOS-7
# tree.
#
# At this point in 7.0.1406, we have no older release
[root@CentOS70 ilan]#



I need to old kernels because the module i write need to compile on these kernels, if my customers are using these kernels (and thats why i need to compile the module against), its their problem. i just need to support these kernels i am not their CIO

[TrevorH]

You should look at how ELRepo build their kernel modules as those survive kernel updates except at point release times when the kernel ABI changes. That way you can limit it to one version per point release (or until RH change the ABI by mistake!).

[jlehtone]

Code: Select all

$ tail -1 /etc/yum.repos.d/CentOS-Vault.repo
# At this point in 7.0.1406, we have no older release

In other words you have applied next to no updates at all since the first release of CentOS 7.


If your customers are using CentOS 7, then they have no excuse to use anything but the latest kernel. Like you said, that is their problem.

If they are using RHEL 7, then they could stick to an earlier point release. I don't know whether Red Hat releases kernel updates to those paying customers. If it does, then you don't have access to all their kernels anyway and the only option is, like Trevor said, to build version independent kernel modules in ELRepo style and hope that they work with the inaccessible kernels.


I would start with fully updated CentOS 7 and then see for which older kernels I can compile in that environment. Alternatively/in addition spawn one instance per older point update, i.e. 7.0, 7.1, 7.2, and 7.3 with all updates that they ever did get.