I'm running Fedora-19/KDE on a Thinkpad T61. I had serious problems with hibernation when kernel-3.11 first came on the scene. Things have slightly improved now, but I still occasionally have what seems like the same problem, one symptom being that I cannot shutdown except by pressing the power button.
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
On Wed, Oct 9, 2013 at 6:40 PM, Timothy Murphy gayleard@eircom.net wrote:
I'm running Fedora-19/KDE on a Thinkpad T61. I had serious problems with hibernation when kernel-3.11 first came on the scene. Things have slightly improved now, but I still occasionally have what seems like the same problem, one symptom being that I cannot shutdown except by pressing the power button.
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
If nothing else as long as it is the kernel that is running it won't be removed during an update.
John
Allegedly, on or about 10 October 2013, Timothy Murphy sent:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
Simplistic solution, set yum to keep something like 5, or more, kernels. So that it's so long before it automatically removes one, that you've still got the one that you want. And that gives you much more time to see whether any new kernels do work adequately. You can manually remove in-between versions.
I do that, for all installs. I've had kernel problems in the past, and I want to ensure that I've got plenty of fallbacks to try out. Sometimes you don't notice a problem with a new kernal for quite some time.
However, I think you could list the exact version that you want to exclude. The yum.conf man file, for older releases, at least, mentions that wildcarding is *allowed*, it doesn't say wildcarding has to be used.
Tim wrote:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
Simplistic solution, set yum to keep something like 5, or more, kernels. So that it's so long before it automatically removes one, that you've still got the one that you want. And that gives you much more time to see whether any new kernels do work adequately. You can manually remove in-between versions.
Thanks for your response, which was very helpful. I've set installonly_limit=6 in /etc/yum.conf . I'm still having problems with kernel-3.11 , though less than was the case, I think.
However, I think you could list the exact version that you want to exclude.
I'm not quite sure of the logic of "yum --exclude=kernel-PAE-devel-3.10.* update"
On Thu, 10 Oct 2013 01:40:41 +0200 Timothy Murphy gayleard@eircom.net wrote:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
# su # echo kernel-you-want-to-keep >> /etc/yum/protected.d/kernel.conf
On Thu, 10 Oct 2013 08:36:18 +0100 Frank Murphy frankly3d@gmail.com wrote:
On Thu, 10 Oct 2013 01:40:41 +0200 Timothy Murphy gayleard@eircom.net wrote:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
# su # echo kernel-you-want-to-keep >> /etc/yum/protected.d/kernel.conf
Scrap that idea, forgot the kernel follows it own rules.
On 10/09/2013 07:40 PM, Timothy Murphy wrote:
I'm running Fedora-19/KDE on a Thinkpad T61. I had serious problems with hibernation when kernel-3.11 first came on the scene. Things have slightly improved now, but I still occasionally have what seems like the same problem, one symptom being that I cannot shutdown except by pressing the power button.
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
Hers is how to do it.
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
Do a rpm -qa | grep kernel and something like this will appear ;
$ rpm -qa | grep kernel kernel-3.9.3-201.fc18.i686 kernel-modules-extra-3.9.2-200.fc18.i686 kernel-3.6.10-4.fc18.i686 abrt-addon-kerneloops-2.1.7-1.fc18.i686 kernel-modules-extra-3.6.10-4.fc18.i686 kernel-modules-extra-3.9.3-201.fc18.i686 kernel-3.9.2-200.fc18.i686 libreport-plugin-kerneloops-2.1.7-1.fc18.i686
Goto /etc/yum/pluginconf.d/versionlock.list and open empty file, in this file copy and paste, example;
kernel-3.9.3-201.fc18.i686 kernel-modules-extra-3.9.3-201.fc18.i686
Which is latest kernel, and yum will no longer update kernel and dep. packages. Save versionlock.list and go back to enjoying Fedoraa.
On Thu, 10 Oct 2013 10:13:30 -0400 Jim binarynut@comcast.net wrote:
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
He still want to be able to update kernel, What he may be able to do is backup, needed initramfs, vmlinuz, and config to /boot/backup,
use that in kernel line as and when required? Havn't tested this theory.
On 10/10/2013 10:17 AM, Frank Murphy wrote:
On Thu, 10 Oct 2013 10:13:30 -0400 Jim binarynut@comcast.net wrote:
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
He still want to be able to update kernel, What he may be able to do is backup, needed initramfs, vmlinuz, and config to /boot/backup,
use that in kernel line as and when required? Havn't tested this theory.
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
On Thu, 10 Oct 2013 10:34:34 -0400 David dgboles@gmail.com wrote:
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
So basically keep the kernel*.rpm, and rpm --force when necessary, along with grub2-mkconfig...
On 10/10/2013 10:44 AM, Frank Murphy wrote:
On Thu, 10 Oct 2013 10:34:34 -0400 David dgboles@gmail.com wrote:
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
So basically keep the kernel*.rpm, and rpm --force when necessary, along with grub2-mkconfig...
If you have the kernel-<some_name>.rpm you can install it with
yum localinstall <kernel-some_name>
or
rpm -ivh <kernel-some_name>
after it installs dracut will run and that creates these files
BTW FYI
http://en.wikipedia.org/wiki/Vmlinux
http://en.wikipedia.org/wiki/Initramfs
http://en.wikipedia.org/wiki/Initramfs
I *do not know* if it is necessary to run grub2-mkconfig. It would not hurt. You would have to select this kernel from the menu at boot.
On 10 October 2013 15:34, David dgboles@gmail.com wrote:
On 10/10/2013 10:17 AM, Frank Murphy wrote:
On Thu, 10 Oct 2013 10:13:30 -0400 Jim binarynut@comcast.net wrote:
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
He still want to be able to update kernel, What he may be able to do is backup, needed initramfs, vmlinuz, and config to /boot/backup,
use that in kernel line as and when required? Havn't tested this theory.
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
Those files *include* the kernel (vmlinuz) and if you wanted you could manually put them there after removing the package. (You'd also want the relevant /lib/modules directory too, and probably the relevant kernel headers) That said, advice on methods to avoid uninstalling the package in the first place is probably the best strategy.
On 10/10/2013 12:53 PM, Ian Malone wrote:
On 10 October 2013 15:34, David dgboles@gmail.com wrote:
On 10/10/2013 10:17 AM, Frank Murphy wrote:
On Thu, 10 Oct 2013 10:13:30 -0400 Jim binarynut@comcast.net wrote:
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
He still want to be able to update kernel, What he may be able to do is backup, needed initramfs, vmlinuz, and config to /boot/backup,
use that in kernel line as and when required? Havn't tested this theory.
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
Those files *include* the kernel (vmlinuz) and if you wanted you could manually put them there after removing the package. (You'd also want the relevant /lib/modules directory too, and probably the relevant kernel headers) That said, advice on methods to avoid uninstalling the package in the first place is probably the best strategy.
You should read my other post in this thread where I linked explanations about the files.
And the big question is *why* would anyone want to do that?
Sadly the options are:
New kernels no longer work with your older, or odd, hardware then don't update the kernel. Which also leaves you with not being about to update to new OS version(s).
Or?
Replace the the older, or odd, hardware.
Life goes on.
On 10 October 2013 19:00, David dgboles@gmail.com wrote:
On 10/10/2013 12:53 PM, Ian Malone wrote:
On 10 October 2013 15:34, David dgboles@gmail.com wrote:
On 10/10/2013 10:17 AM, Frank Murphy wrote:
On Thu, 10 Oct 2013 10:13:30 -0400 Jim binarynut@comcast.net wrote:
In Fedora repo there is a package named "yum-plugin-versionlock-1.1.31-10.fc18.noarch" install it.
He still want to be able to update kernel, What he may be able to do is backup, needed initramfs, vmlinuz, and config to /boot/backup,
use that in kernel line as and when required? Havn't tested this theory.
These 'kernel files' are created when a kernel installed and they are specific for *that* kernel. They do not work with older or newer kernels. If *this* kernel is removed they no longer have any value. If you re-install that kernel these files are recreated.
Those files *include* the kernel (vmlinuz) and if you wanted you could manually put them there after removing the package. (You'd also want the relevant /lib/modules directory too, and probably the relevant kernel headers) That said, advice on methods to avoid uninstalling the package in the first place is probably the best strategy.
You should read my other post in this thread where I linked explanations about the files.
I saw it. You suggested that dracut creates these files, it only creates the initramfs image. The post I replied to (above) actually says the files are dependent on and specific to the kernel, rather than that these are the installed kernel and related files. It creates confusion (whether or not you are confused yourself) between the package and the kernel itself. I thought that was worth clarifying.
Sadly the options are:
New kernels no longer work with your older, or odd, hardware then don't update the kernel. Which also leaves you with not being about to update to new OS version(s).
Or?
Replace the the older, or odd, hardware.
Or
Report a bug and try to get a regression fixed. The new kernels don't work problem should only happen when support for something is dropped. (Or if you rely on a proprietary module.)
On Thu, 10 Oct 2013 01:40:41 +0200 Timothy Murphy gayleard@eircom.net wrote:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
This should cover this problem (James works on yum) http://lists.baseurl.org/pipermail/yum/2013-October/024030.html
Frank Murphy wrote:
In any case, I have one 3.10 kernel in my three grub kernels. I'm yum-updating with exclude=kernel* to avoid losing this kernel. But I'm wondering if there is some way of telling yum that I want to keep this kernel, but would like to update the current kernel?
This should cover this problem (James works on yum) http://lists.baseurl.org/pipermail/yum/2013-October/024030.html
This suggests "yumdb set installonly keep kernel-nnn" does what you want.
I'm not quite sure what nnn is in this case. I want to keep kernel-PAE-3.10.11-200.fc19.i686
On Mon, 14 Oct 2013 22:11:56 +0200 Timothy Murphy gayleard@eircom.net wrote: http://lists.baseurl.org/pipermail/yum/2013-October/024030.html
This suggests "yumdb set installonly keep kernel-nnn" does what you want.
I'm not quite sure what nnn is in this case. I want to keep kernel-PAE-3.10.11-200.fc19.i686
nnn just represents what comes behind the kernel bit which from yuor line above should be: "yumdb set installonly keep kernel-PAE-3.10.11-200.fc19.i686"
-
David -
Frank Murphy -
Ian Malone -
inode0 -
Mickey -
Tim -
Timothy Murphy