Hi,
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9) and to remove 3.2.5 instead (the middle one)? (There is the possibility to remove the middle kernel before each updates, but it's not really convenient).
On Thu, Feb 23, 2012 at 11:07 AM, enclair wifienclair@gmail.com wrote:
Hi,
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9) and to remove 3.2.5 instead (the middle one)? (There is the possibility to remove the middle kernel before each updates, but it's not really convenient).
You could change the installonly_limit in /etc/yum.conf. If you set it to 0, yum won't remove any kernels when a new one is installed. You could then remove unwanted ones manually at your convenience.
-T.C.
Yes I could do that, thank you. (However, it must be set to "keep" I think, not "0", according to man yum.conf).
Le 23 février 2012 19:13, T.C. Hollingsworth tchollingsworth@gmail.com a écrit :
On Thu, Feb 23, 2012 at 11:07 AM, enclair wifienclair@gmail.com wrote:
Hi,
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9)
and to
remove 3.2.5 instead (the middle one)? (There is the possibility to remove the middle kernel before each
updates,
but it's not really convenient).
You could change the installonly_limit in /etc/yum.conf. If you set it to 0, yum won't remove any kernels when a new one is installed. You could then remove unwanted ones manually at your convenience.
-T.C.
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Thu, Feb 23, 2012 at 11:51 AM, enclair wifienclair@gmail.com wrote:
Yes I could do that, thank you. (However, it must be set to "keep" I think, not "0", according to man yum.conf).
"keep" is a value set in the YUM database. "0" is what you set installonly_limit to prevent YUM from removing installonly packages.
From the manpage, note the added emphasis:
installonly_limit Number of packages listed in installonlypkgs to keep installed at the same time. __Setting to 0 disables this feature.__ Default is '3'. Note that this functionality used to be in the "installonlyn" plugin, where this option was altered via. tokeep. Note that as of version 3.2.24, yum will now __look in the yumdb__ for a installonly attribute on installed packages. If __that attribute is "keep",__ then they will never be removed.
-T.C.
I was wrong.
Le 23 février 2012 20:20, T.C. Hollingsworth tchollingsworth@gmail.com a écrit :
On Thu, Feb 23, 2012 at 11:51 AM, enclair wifienclair@gmail.com wrote:
Yes I could do that, thank you. (However, it must be set to "keep" I think, not "0", according to man yum.conf).
"keep" is a value set in the YUM database. "0" is what you set installonly_limit to prevent YUM from removing installonly packages.
From the manpage, note the added emphasis:
installonly_limit Number of packages listed in installonlypkgs to keep installed at the same time. __Setting to 0 disables this feature.__ Default is '3'. Note that this functionality used to be in the "installonlyn" plugin, where this option was altered via. tokeep. Note that as of version 3.2.24, yum will now __look in the yumdb__ for a installonly attribute on installed packages. If __that attribute is "keep",__ then they will never be removed.
-T.C.
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 23/02/12 18:07, enclair wrote:
Hi,
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9)
Get a copy of the kernel you want to to keep from http://koji.fedoraproject.org/koji/ search kernel
Put it some-place safe, then when yum removes it, you just reinstall it.
On Thu, 23 Feb 2012, enclair wrote:
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9) and to remove 3.2.5 instead (the middle one)? (There is the possibility to remove the middle kernel before each updates, but it's not really convenient).
You could make sure you are running on the kernel you want to keep as yum won't remove the running kernel.
Michael Young
De: M A Young m.a.young@durham.ac.uk Para: Community support for Fedora users users@lists.fedoraproject.org Enviado: Jueves, 23 de febrero, 2012 15:29:49 Asunto: Re: How to keep a particular kernel version?
On Thu, 23 Feb 2012, enclair wrote:
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6 There is a new kernel in -updates (3.2.7). If I update to the new kernel, yum will want to remove 3.1.9. Is there a possibility to set up yum to keep the older kernel (3.1.9) and to remove 3.2.5 instead (the middle one)? (There is the possibility to remove the middle kernel before each updates, but it's not really convenient).
You could make sure you are running on the kernel you want to keep as yum won't remove the running kernel.
Michael Young -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Yum is configured to keep 3 kernels. If you remove the middle one 3.2.5 manually, when yum runs it shouldn't remove any kernels since you only have 2. Alternately, you can configure yum to keep more than 3 kernels. But that will take up more disk space unnecessarily.
DK
On 23/02/12 18:07, enclair wrote:
Hi,
Is there a possibility to set up yum to keep the older kernel
Thinking about this. NB *Your entries may look different
Rename the one you want to keep. Try from: menuentry 'Fedora (3.2.7-1.fc16.x86_64)' --class fedora --class gnu-linux --class gnu --class os {
to: menuentry 'Keep-Me (3.2.7-1.fc16.x86_64)' --class fedora --class gnu-linux --class gnu --class os {
Maybe also: echo 'Loading Fedora (3.2.7-1.fc16.x86_64)' to: echo 'Loading Keep-Me (3.2.7-1.fc16.x86_64)'
On 02/25/2012 06:20:22 AM, Frank Murphy wrote:
On 23/02/12 18:07, enclair wrote:
Hi,
Is there a possibility to set up yum to keep the older kernel
Thinking about this. NB *Your entries may look different
Rename the one you want to keep. Try from: menuentry 'Fedora (3.2.7-1.fc16.x86_64)' --class fedora --class gnu-linux --class gnu --class os {
to: menuentry 'Keep-Me (3.2.7-1.fc16.x86_64)' --class fedora --class gnu-linux --class gnu --class os {
Maybe also: echo 'Loading Fedora (3.2.7-1.fc16.x86_64)' to: echo 'Loading Keep-Me (3.2.7-1.fc16.x86_64)'
In which file are these changes made?
head -n 6 /etc/grub2.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub #
Le 25 février 2012 18:16, Frank Murphy frankly3d@gmail.com a écrit :
On 25/02/12 16:48, Geoffrey Leach wrote:
In which file are these changes made?
/etc/grub2.cfg
On 26/02/12 11:19, enclair wrote:
head -n 6 /etc/grub2.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub #
It didn't work anyway. Yum still pulled it out.
What did work in a test was:
copy /etc/grub2.cfg keep it safe somewhere. copy the relevant kernel bits from /boot keep them safe also. The next kernel update, merge the two copies of /etc/grub2.cfg
Copy the saved kernel bits back. Now yum\rpm doesn't know anything about this kernel.
-
Dennis Kaptain -
enclair -
Frank Murphy -
Geoffrey Leach -
M A Young -
T.C. Hollingsworth