https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c1 --- Comment #1 from Michael Meeks 2008-05-21 04:16:11 MST --- Created an attachment (id=217190) --> (https://bugzilla.novell.com/attachment.cgi?id=217190) zipped zypper strace -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c3 --- Comment #3 from Michael Meeks 2008-05-21 04:21:00 MST --- Created an attachment (id=217195) --> (https://bugzilla.novell.com/attachment.cgi?id=217195) y2logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c5 Andreas Gruenbacher changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |aosthof@novell.com --- Comment #5 from Andreas Gruenbacher 2008-05-22 03:16:19 MST --- Alex, could you please have a look at what's going on here with the interaction with perl-Bootloader? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c7 --- Comment #7 from Alexander Osthof 2008-05-27 08:54:34 MDT --- Alright, I think I've found the problem: Investigating the file perl-BL-standalone-log (included in attached YaST2 logs) one can see that following sections (which get misleadingly removed) are using symlinks for kernel and initrd instead of the full file names: --------------------------------------------------------------------------- 2008-05-13 17:36:51 MILESTONE: GRUB::Parselines: input from menu.lst : '# Modified by YaST2. Last modification on Thu May 8 15:12:16 BST 2008' ' default 0' ' timeout 8' ' gfxmenu (hd1,2)/message' ' ' ' ###Don't change this comment - YaST2 identifier: Original name: linux###' ' title openSUSE' ' root (hd1,2)' ' kernel /vmlinuz root=/dev/disk/by-id/scsi-SATA_Maxtor_6Y120P0_Y3NF4VFE-part5 resume=/dev/md0 splash=silent showopts vga=0x317' ' initrd /initrd' [snip] ' ###Don't change this comment - YaST2 identifier: Original name: failsafe###' ' title Failsafe -- openSUSE' ' root (hd1,2)' ' kernel /vmlinuz root=/dev/disk/by-id/scsi-SATA_Maxtor_6Y120P0_Y3NF4VFE-part5 showopts ide=nodma apm=off acpi=off noresume edd=off x1 1failsafe vga=0x317' ' initrd /initrd' --------------------------------------------------------------------------- After installing the kernel-debug package, those symlinks get adjusted to point to the kernel-debug files, thus "vmlinuz-2.6.25.3-2-debug" and "initrd-2.6.25.3-2-debug". Eventually, when the kernel-debug package gets removed afterwards, the above mentioned 2 sections are also matching because their symlinks get resolved, point to the same files and so get removed, too. So, the question is where those sections using symlinks stem from? I'm asking because after a fresh installation of openSUSE long names are used, so are they after an update using rpm or zypper. Concerning the additional and unwanted xen kernel - I don't have a clue. There's no dependency in perl-Bootloader which trigger xen kernels to get installed or removed. Maybe some zypper dependency? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c9 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #9 from Alexander Osthof 2008-05-29 06:27:13 MDT --- Sorry, but I have to disappoint you. In both cases of either a fresh installation or and "normal" kernel update long names of images (vmlinuz & initrd) will be entered in the menu.lst, e.g. "vmlinuz-2.6.22.17-0.1-default" or "initrd-2.6.22.17-0.1-default", to avoid above described confusions. Using symlinks for those file as in your case most likely stems from a manual intervention, thus there's nothing systematic I can do. Changing the symlinks (thus let them point to a new image) even happens in the post install/uninstall script of kernel packages, which I'm not responsible for. And I don't think this will be changed due to legacy issues IMHO. Closing bug RESOLVED INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User roland.kletzing@materna.de added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c11 --- Comment #11 from roland kletzing 2008-05-29 11:37:24 MDT --- Alexander, thanks for looking at that. i'm not sure if this really is resolved. iirc, i never use symlinks. if is see an entry in grub pointing to a symlink, the first thing i`m doing is adjusting the entry to point to the full path. so my issue was different. will reopen or post another bug report if i have a proper repro-case... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c13 Michael Meeks changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical Status|RESOLVED |REOPENED Resolution|INVALID | Summary|kernel install/remove leaves broken system ... |live-CD kernel install/remove leaves broken | |system ... Version|Beta 2 |RC 1 --- Comment #13 from Michael Meeks 2008-06-02 03:47:46 MDT ---

Sorry, but I have to disappoint you. In both cases of either a fresh installation or and "normal" kernel update long names of images (vmlinuz & initrd) will be entered in the menu.lst, e.g. "vmlinuz-2.6.22.17-0.1-default" or "initrd-2.6.22.17-0.1-default", to avoid above described confusions.

Re-opening & bumping priority - I just did a live-CD install of RC1; and my /boot/grub/menu.lst emphatically uses symlinks to initrd and vmlinuz: $ ls -l /boot total 12644 .. drwxr-xr-x 2 root root 4096 Jun 2 09:42 grub lrwxrwxrwx 1 root root 25 Jun 2 09:42 initrd -> initrd-2.6.25.4-8-default -rw-r--r-- 1 root root 5777149 Jun 2 09:42 initrd-2.6.25.4-8-default .. lrwxrwxrwx 1 root root 26 Jun 2 09:36 vmlinuz -> vmlinuz-2.6.25.4-8-default -rw-r--r-- 1 root root 2125760 May 27 01:47 vmlinuz-2.6.25.4-8-default $ cat grub/menu.lst # Modified by YaST2. Last modification on Mon Jun 2 09:42:30 BST 2008 default 0 timeout 8 gfxmenu (hd0,5)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.0 root (hd0,5) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-SATA_WDC_WD800BB-75FWD-WCAJD1497090-part6 resume=/dev/sda5 splash=silent showopts vga=0x305 initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,5) chainloader (hd0,1)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,5) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.0 root (hd0,5) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-SATA_WDC_WD800BB-75FWD-WCAJD1497090-part6 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x305 initrd /boot/initrd

Using symlinks for those file as in your case most likely stems from a manual intervention, thus there's nothing systematic I can do. Changing the symlinks (thus let them point to a new image) even happens in the post install/uninstall script of kernel packages, which I'm not responsible for. And I don't think this will be changed due to legacy issues IMHO.

Quite possibly this is a live-CD specific problem; re-opening & upping priority. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c16 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker --- Comment #16 from Stephan Kulow 2008-06-03 03:36:08 MDT --- ok, I verified the bug is evil: zypper in kernel-pae -> I get pae entries twice in menu.lst (the default is gone) zypper rm kernel-pae -> no kernel left at all -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c18 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aosthof@novell.com |juhliarik@novell.com Status|REOPENED |NEW --- Comment #18 from Stephan Kulow 2008-06-03 07:47:21 MDT --- ok, #17 is invalid. The other sections were removed because there was no valid initrd entry. The real bug is that the live installer uses /vmlinuz and not the name. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c19 --- Comment #19 from Stephan Kulow 2008-06-03 16:34:16 MDT --- do I read the logs right, that it thought kernel-pae would have been the better kernel and is confused because still kernel-default was installed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=393030 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c21 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #21 from Jozef Uhliarik 2008-06-04 02:46:35 MDT --- problem with solving simlinks for kernel and initrd is fixed in yast2-bootloader version 2.16.18 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.