[SLE] Keeping previous kernel installations
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime? Thanks, LDB -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions. /Per Jessen, Zürich -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions.
I thought a kernel update kept the previous kernel as: vmlinuz.previous and initrd.previous It doesn't make an entry in the grub menu.lst for these but they should be available and you should be able to make a boot entry for them. (and you can make that entry on the fly if you have to - at boot time) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Am Sonntag, 11. Juni 2006 19:17 schrieb Bruce Marshall:
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions.
I thought a kernel update kept the previous kernel as:
vmlinuz.previous and initrd.previous
in which directory is this vmlinuz.previous? It's not in /boot on my 10.0. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 11 June 2006 13:32, Daniel Bauer wrote:
Am Sonntag, 11. Juni 2006 19:17 schrieb Bruce Marshall:
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions.
I thought a kernel update kept the previous kernel as:
vmlinuz.previous and initrd.previous
in which directory is this vmlinuz.previous? It's not in /boot on my 10.0.
It is on mine.... Have you done a kernel update? lrwxrwxrwx 1 root root 24 2006-06-03 13:18 vmlinuz -> vmlinuz-2.6.13-15.10-smp -rw-r--r-- 1 root root 1542697 2006-05-12 12:27 vmlinuz-2.6.13-15.10-default -rw-r--r-- 1 root root 1684966 2006-05-12 12:22 vmlinuz-2.6.13-15.10-smp lrwxrwxrwx 1 root root 28 2006-06-03 13:17 vmlinuz.previous -> vmlinuz-2.6.13-15.10-default Mine shows that the previous was the default of the same level kernel (not SMP) because Yast always picks the wrong kernel for my HT machine. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Daniel Bauer wrote:
Am Sonntag, 11. Juni 2006 19:17 schrieb Bruce Marshall:
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions.
I thought a kernel update kept the previous kernel as:
vmlinuz.previous and initrd.previous
in which directory is this vmlinuz.previous? It's not in /boot on my 10.0.
Daniel
Same here .. LDB -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 11 June 2006 20:22, LDB wrote:
Daniel Bauer wrote:
Am Sonntag, 11. Juni 2006 19:17 schrieb Bruce Marshall:
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions.
I thought a kernel update kept the previous kernel as:
vmlinuz.previous and initrd.previous
in which directory is this vmlinuz.previous? It's not in /boot on my 10.0.
Daniel
Same here ..
LDB
It must be a 10.1 change - found it in /boot [/boot] [20:27:26 peter]$ l *.previous lrwxrwxrwx 1 root root 26 2006-05-04 10:47 initrd.previous -> initrd-2.6.16.12-3-default lrwxrwxrwx 1 root root 22 2006-05-04 10:33 initrd-xen.previous -> initrd-2.6.16.12-3-xen lrwxrwxrwx 1 root root 27 2006-05-04 10:47 vmlinuz.previous -> vmlinuz-2.6.16.12-3-default lrwxrwxrwx 1 root root 23 2006-05-04 10:33 vmlinuz-xen.previous -> vmlinuz-2.6.16.12-3-xen [/boot] plus its mentioned in grub as an entry. SLES9 SP3 doesn't have it, and I don't believe I ever say it on 9.3 or 10.0 Cheers Pete -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Pete Connolly wrote:
On Sunday 11 June 2006 20:22, LDB wrote:
Daniel Bauer wrote:
Am Sonntag, 11. Juni 2006 19:17 schrieb Bruce Marshall:
On Sunday 11 June 2006 13:00, Per Jessen wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime? I don't know how you configure SUSE Linux, but you can always just install the kernel versions you want, and then correct your lilo/grub configuration separately. It's very handy for trying out different kernel versions. I thought a kernel update kept the previous kernel as:
vmlinuz.previous and initrd.previous in which directory is this vmlinuz.previous? It's not in /boot on my 10.0.
Daniel Same here ..
LDB
It must be a 10.1 change - found it in /boot
[/boot] [20:27:26 peter]$ l *.previous lrwxrwxrwx 1 root root 26 2006-05-04 10:47 initrd.previous -> initrd-2.6.16.12-3-default lrwxrwxrwx 1 root root 22 2006-05-04 10:33 initrd-xen.previous -> initrd-2.6.16.12-3-xen lrwxrwxrwx 1 root root 27 2006-05-04 10:47 vmlinuz.previous -> vmlinuz-2.6.16.12-3-default lrwxrwxrwx 1 root root 23 2006-05-04 10:33 vmlinuz-xen.previous -> vmlinuz-2.6.16.12-3-xen [/boot]
plus its mentioned in grub as an entry. SLES9 SP3 doesn't have it, and I don't believe I ever say it on 9.3 or 10.0
Cheers
Pete
I can tell for sure that 9.3 and 10.0 have old kernel removed, as I still use 10.0 most of the time, and have backup machine with 9.3. This might be one more reason to begin using 10.1 more. -- Regards, Rajko. Visit http://en.opensuse.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
Thanks,
LDB
I guess the problem is that YaST removes old version from /boot directory. If you compile kernel from sources this should not happen, but you have to edit /boot/grub/menu.lst anyway. You can make renamed copies of kernel and initrd and add an entry in /boot/grub/menu.lst that will point to old versions. After that you can install new, update current via YOU, but good old boot that works will wait for you for in case that new version can't boot the system. YaST will not touch manually added entries. -- Regards, Rajko. Visit http://en.opensuse.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Rajko M wrote:
LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
Thanks,
LDB
I guess the problem is that YaST removes old version from /boot directory.
If you compile kernel from sources this should not happen, but you have to edit /boot/grub/menu.lst anyway.
You can make renamed copies of kernel and initrd and add an entry in /boot/grub/menu.lst that will point to old versions. After that you can install new, update current via YOU, but good old boot that works will wait for you for in case that new version can't boot the system. YaST will not touch manually added entries.
yes, I can do that but I do not want to that unless I have to do so. I was hoping there was something in /etc/sysconfig/kernel to do what I as desiring. Maybe there is something is YaST2 that can help me. If not, I will have to resort to compilations. Thanks everyone, LDB -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 11 June 2006 18:38, LDB wrote:
When I upgrade to any subsequent kernel that SuSE updates to, my current kernel package get removed. How do configure the 10.0 and 10.1 to NOT remove the older kernel but just make it available to boot at anytime?
Instead of the -U option, use the -i option: rpm -ihv <path_to_kernel.rpm> And have a look at /boot afterwards. ;) Cheers, Leen -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (7)
-
Bruce Marshall -
Daniel Bauer -
LDB -
Leendert Meyer -
Per Jessen -
Pete Connolly -
Rajko M