[Bug 252911] New: installing the 10.2 kernel update changes the menu.lst file in unexpected ways
https://bugzilla.novell.com/show_bug.cgi?id=252911 Summary: installing the 10.2 kernel update changes the menu.lst file in unexpected ways Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: stefan.fent@novell.com ReportedBy: meissner@novell.com QAContact: qa@suse.de CC: kssingvo@novell.com We have several reports of the current 10.2 kernel update (released yesterday) changing the /boot/grub/menu.lst in interesting ways. I just reproduced this on my machine: - it created a new entry "2.6.18.8-0.1-default" and made it the default instead of keeping the openSUSE 10.2 entry as default -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #1 from meissner@novell.com 2007-03-09 03:29 MST ------- Created an attachment (id=123417) --> (https://bugzilla.novell.com/attachment.cgi?id=123417&action=view) menu.lst.before saved copy of menu.lst right before update -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #2 from meissner@novell.com 2007-03-09 03:30 MST ------- Created an attachment (id=123418) --> (https://bugzilla.novell.com/attachment.cgi?id=123418&action=view) menu.lst.after menu.lst afterwards -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #4 from mboman@novell.com 2007-03-09 03:37 MST ------- FYI; This is not new.. It's been happening for a while. And this is also happening on openSUSE 10.3 at the moment. Here's the output from my menu.lst on a 10.3 install after a few kernel updates; title openSUSE 10.3 title Failsafe -- openSUSE 10.3 title Kernel-2.6.20-rc7-2-default title Kernel-2.6.20-5-default title Kernel-2.6.20-6-default title Kernel-2.6.20-9-default -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #5 from meissner@novell.com 2007-03-09 03:43 MST ------- on another machine it removes the openSUSE 10.2 entry alltogether ... attaching 3 more files. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #6 from meissner@novell.com 2007-03-09 03:44 MST ------- Created an attachment (id=123425) --> (https://bugzilla.novell.com/attachment.cgi?id=123425&action=view) westernhagen.menu.lst.before menu.lst before update with lots of installed other entries -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #7 from meissner@novell.com 2007-03-09 03:44 MST ------- Created an attachment (id=123426) --> (https://bugzilla.novell.com/attachment.cgi?id=123426&action=view) westernhagen.menu.lst.after after update -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #8 from meissner@novell.com 2007-03-09 03:45 MST ------- Created an attachment (id=123427) --> (https://bugzilla.novell.com/attachment.cgi?id=123427&action=view) westernhagen.diff and diff. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 mboman@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbronczyk@novell.com ------- Comment #9 from mboman@novell.com 2007-03-09 03:47 MST ------- *** Bug 252915 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #10 from meissner@novell.com 2007-03-09 03:48 MST ------- both systems still boot btw. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #11 from meissner@novell.com 2007-03-09 04:42 MST ------- german comment from reporter: Hallo, das seit gestern verfügbare Kernel-Update für die openSUSE 10.2 auf 2.6.18.8-0.1-default verstümmelt das Grub-Menü: - der Failsafe-Eintrag verschwindet - der Eintrag "title openSUSE 10.2" verschwindet - "title Kernel-2.6.18.8-0.1-default" wird hinzugefügt Genaugenommen werden offenbar kurz nacheinander zwei menu.lst erzeugt, eine wird dann zu menu.lst.old (beide mit unterschiedlichen Inhalten), die kürzere Version bleibt übrig. Ist hier schon auf zwei Maschinen reproduzierbar. Vielleicht wollt Ihr das noch fixen, ehe das Announcement kommt? Beste Grüße J. Schönberg -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 meissner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joe@pdi-berlin.de ------- Comment #12 from meissner@novell.com 2007-03-09 04:43 MST ------- ccing above reporter -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 meissner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.fent@novell.com AssignedTo|stefan.fent@novell.com |jplack@novell.com ------- Comment #13 from meissner@novell.com 2007-03-09 04:45 MST ------- reassign to perl-Bootloader maintainer. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 stefan.fent@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jplack@novell.com |aosthof@novell.com ------- Comment #14 from stefan.fent@novell.com 2007-03-09 05:42 MST ------- reassign to new perl-Bootloader Maintainer ;-) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #15 from kssingvo@novell.com 2007-03-09 05:54 MST ------- happened at my AMD64 machine at home too. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #16 from meissner@novell.com 2007-03-09 05:57 MST ------- what we also saw is that if you had -default and -xen it might just switch to the one last updated. (from -default -> -xen in one 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #17 from stefan.fent@novell.com 2007-03-09 07:00 MST ------- Talking about 10.2, ignoring 10.3 (different problems) Normally, if you have installed openSUSE 10.2, the entry with the openSUSE 10.2 label should not disappear, as it still usese the /boot/vmlinuz link. So does the Failsafe entry. You will get a new entry upon update, with the Kernel-... Label, which then is default. I don't know how Marcus came to the openSUSE-10.2 entry pointing to the image, not the link (comment #6) Having to create a new entry for a new kernel comes from the requirement to be able to install more than 2 kernels, on older distributions we used the link and an additional 'previous' link -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #18 from stefan.fent@novell.com 2007-03-09 07:22 MST ------- A suggestion: openSUSE 10.2 -- Kernel-2.6.18.8-0.1-default instead of Kernel-2.6.18.8-0.1-default -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #19 from joe@pdi-berlin.de 2007-03-09 12:57 MST ------- No, I think most users are not interested in seeing the kernel number. "openSUSE 10.2" just would be OK. I just tested a third 10.2 system. Same behaviour: 1. Before kernel update - 3 entries in menu.lst: ################################################ title openSUSE 10.2 .. title Windows .. title Failsafe -- openSUSE 10.2 .. 2. after update: ################## ls -la -rw------- 1 root root 479 Mar 9 18:10 menu.lst -rw------- 1 root root 1073 Mar 9 18:10 menu.lst.old Entries in menu.lst.old: ########################## title openSUSE 10.2 .. title Windows .. title Failsafe -- openSUSE 10.2 .. title Kernel-2.6.18.8-0.1-default .. entries in menu.lst: #################### title Windows .. title Kernel-2.6.18.8-0.1-default .. ->>> "openSUSE 10.2" has gone, "Failsafe" has gone!!! Joe -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma2412ma@hotmail.com ------- Comment #20 from judas_iscariote@shorewall.net 2007-03-09 14:58 MST ------- *** Bug 252938 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rafpolak@o2.pl ------- Comment #21 from judas_iscariote@shorewall.net 2007-03-09 19:08 MST ------- *** Bug 253318 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ast@novell.com, aj@novell.com Priority|P5 - None |P1 - Urgent ------- Comment #22 from aj@novell.com 2007-03-10 12:47 MST ------- Please investigate and fix this and let's release an update for 10.2! -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #23 from jengelh@gmx.de 2007-03-10 13:15 MST ------- JFYI: The bug, as per comment #1, also happens (rightfully!) when having multiple kernels installed alongside each other. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #24 from Chananko@yahoo.com 2007-03-10 18:37 MST ------- In addition to the menu list being permanently changed.(I switched back to 2.6.18.2 and my menu remains listed as 2.6.18.2 default kernel). When I rebooted, the system would not launch the wallpaper in gnome sessions nor the icons (nautilus). Can the patch for the patch resolve this issue. The icons and wallpaper did come back when I downgraded the kernel. My Grub will have to be changed manually. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #25 from andreas@diestelmann.de 2007-03-11 07:12 MST ------- Created an attachment (id=123669) --> (https://bugzilla.novell.com/attachment.cgi?id=123669&action=view) RAID Device used in root statement instead of disk/partition number The last two menu.lst entries have been generated by kernel package installation and are syntactically wrong for grub. Others have been created by initial system installation. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 andreas@diestelmann.de changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #123669|application/octet-stream |text/plain mime type| | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #26 from Ulrich.Windl@rz.uni-regensburg.de 2007-03-12 00:39 MST ------- While amost discussed to death, I want to be on the CC: for the bug, because I'm also affected with every machine that got the recent kernel update (kernel-default-2.6.18.8-0.1) installed: At the end of /boot/grub/menu.lst, I see a new entry titled "Kernel-2.6.18.8-0.1-default" ("kernel /vmlinuz-2.6.18.8-0.1-default"), and that entry is selected as a new default. On my home system the previous default was to boot Windows, not Linux. I wonder why the entry titled "openSUSE 10.2" ("kernel /vmlinuz") is not good enough for the kernel update. I also think that this is not a critical bug, but an ugly one. Maybe also different issues are reported for this bug. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #27 from stefan.fent@novell.com 2007-03-12 02:29 MST ------- Comment #25: Andreas, can you please open a different bug on your issue, it's not related to this problem. Thanks. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 aosthof@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 jamesrome@alum.mit.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamesrome@alum.mit.edu ------- Comment #28 from jamesrome@alum.mit.edu 2007-03-12 07:28 MST ------- I saw this too. Kind of scary for the non-expert. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com ------- Comment #31 from sbrabec@novell.com 2007-03-13 03:01 MST ------- It makes libata machines unbootable using following line: root (/dev/sda,0) See bug 250654 reported agains 10.3 alpha 1+, which exhibits the same problem. So I am in situation, where old kernel command does not boot properly, because it has no modules any more and new kernel does not boot because it has a broken grub configuration. Could you retract latest kernel update to hide this bug until it will be fixed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #32 from stefan.fent@novell.com 2007-03-13 12:47 MST ------- The problem in comment #31 is not related to this bug - it's most probably a storage problem, which can't be fixed in bootloader configuration code This is about changing hda --> sda AFAICS. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #33 from greg.riedesel@wwu.edu 2007-03-13 17:06 MST ------- I got bit by this one as well. On my machine I boot to Xen by default, and have a "(XEN)" boot option that was generated when I installed the machine. As previous comments have pointed out, I got two new entries on my Grub screen. The old (XEN) entry did not get updated to point to the new kernel, it still references the old and not-present kernel. After the kernel update it turned out that the "Kernel-2.6.18.8-0.1-xen" entry was my default, and that works. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #34 from mike25@wanadoo.nl 2007-03-14 07:22 MST ------- adter the kernelupdate issues,i have reinstalled the old kernel from the opensuse 10.2 dvd, and made a new grub bootloader.Once back in opensuse i opened SMART and locked the kernel, so it won't update. Is there a patch or updated kernel yet, which doesnt cause problems? i am not very good at the command line or manually change grub, so i wait for a good fix or patch that prevents this problem with the kernel update. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #35 from aosthof@novell.com 2007-03-14 07:57 MST ------- A fixed update is in work... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #36 from suse-beta@cboltz.de 2007-03-14 16:46 MST ------- Unfortunately, the system might be unbootable when using lilo because of a broken label. (I don't want to test it - it's a remote server ;-) # lilo Added Linux Added Kernel-2.6. Fatal: Default image doesn't exist. My lilo.conf now: # Modified by YaST2. Last modification on Wed Mar 14 23:32:59 CET 2007 boot = /dev/sda root = /dev/md0 delay = 4 vga = normal default = Kernel-2.6.18.8-0.1-default image = /boot/vmlinuz label = Linux read-only initrd = /boot/initrd vga = 0x314 image = /boot/vmlinuz-2.6.18.8-0.1-default label = Kernel-2.6. <----- Label broken! vga = 0x314 initrd = /boot/initrd-2.6.18.8-0.1-default root = /dev/md0 lilo.conf before kernel update: # Modified by YaST2. Last modification on Do Jan 11 15:11:07 CET 2007 boot = /dev/sda root = /dev/md0 delay = 4 vga = normal default = Linux image = /boot/vmlinuz label = Linux read-only initrd = /boot/initrd vga = 0x314 (+ a commented out entry that got removed, but that's the smallest problem.) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ast@novell.com ------- Comment #37 from sbrabec@novell.com 2007-03-15 05:17 MST ------- Even with grub (and default setup), some SATA/libata systems become unbootable after update (both my two machines became unbootable after the update). Is it possible to remove kernel update until fixing of this bug? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 meissner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ast@novell.com | ------- Comment #38 from meissner@novell.com 2007-03-15 05:23 MST ------- is this realted to the GRUB entry or the KERNEL? If KERNEL -> open a new bug please (and cc me). There have been some SATA changes in the 10.2 tree. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #39 from sbrabec@novell.com 2007-03-15 08:04 MST ------- No, this is related to GRUB entry - it breaks in the exactly same way as 10.3 alpha1+ (bug 250654): This really cannot boot and one have to guess, that "/dev/sda" must be replaced by "hd0": title Kernel-2.6.18.8-0.1-default root (/dev/sda,0) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #40 from meissner@novell.com 2007-03-15 08:08 MST ------- stanislav, what is in /boot/grub/device.map ? did the device name change from hda to sda during this update? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #41 from sbrabec@novell.com 2007-03-16 05:01 MST ------- Yes, the device changed from hda to sda after installation. I did it manually by editing /etc/sysconfig/kernel, /etc/fstab and /boot/grub/menu.lst to work-around bug 232086. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #42 from aj@novell.com 2007-03-16 05:11 MST ------- Stanislav, please file a new Bug please! -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #43 from sbrabec@novell.com 2007-03-16 05:26 MST ------- It's bug 250654. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #44 from stefan.fent@novell.com 2007-03-16 05:41 MST ------- You'll have to change /boot/grub/device.map upfont as well. I suggest to ignore _this_ problem here, it's unrelated to the orginial description. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #45 from aj@novell.com 2007-03-16 06:06 MST ------- Stanislav: The bug you have is really a completely different one. You're not using our 10.2 update kernel as can be seen in bug 232086. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #46 from aj@novell.com 2007-03-16 06:06 MST ------- in comment #45 I meant bug 250654! -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |octo777@charter.net ------- Comment #47 from judas_iscariote@shorewall.net 2007-03-17 00:19 MST ------- *** Bug 255590 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmullagh@verizon.net ------- Comment #48 from judas_iscariote@shorewall.net 2007-03-20 13:33 MST ------- *** Bug 256078 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #49 from aosthof@novell.com 2007-03-21 12:24 MST ------- The fix is mostly complete, but I have to test it properly first to avoid any bad behavior. But a new package will be released soon. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #50 from martin.schlander@gmail.com 2007-03-27 02:06 MST ------- If this is gonna take much longer maybe we could remove the "faulty" kernel update from the servers until it's fixed? Every n00b out there doing a fresh installation is affected by this. I don't know the severity of the security patch in the new kernel, but is this really worth it? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #51 from Theodoros.N@gmail.com 2007-03-27 06:27 MST ------- I would like to say that its not only about "noobs being affected". For me errorous and untested patches are affecting very badly the Novell and Suse reputation. People want reliability as much as security, what to do a secure system if.. you cant boot it? Please do more testing! Dont let final users suffer. Not all have the knowledge to fix a system. Regards and Respect -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #52 from Ulrich.Windl@rz.uni-regensburg.de 2007-03-27 07:29 MST ------- I haven't looked into the postinstall scripts, but the problem seems to be this: The kernel upgrade should be totally independent of boot or module tools, that is it should not contain its own tools. Now there's nothing wrong with the current kernel, but just the way /boot/grub/menu.lst is modified. If some boot tool were broken, we could simply update that, and not the kernel. OK, I looked into the RPM and found: # handle 10.2 and SLES10 SP1 if [ -x /usr/lib/bootloader/bootloader_entry ]; then /usr/lib/bootloader/bootloader_entry \ add \ default \ 2.6.18.8-0.1-default \ vmlinuz-2.6.18.8-0.1-default \ initrd-2.6.18.8-0.1-default [...] When there is in /boot: initrd -> initrd-2.6.18.8-0.1-default vmlinuz -> vmlinuz-2.6.18.8-0.1-default and in menu.lst: title openSUSE 10.2 root (hd0,0) kernel /vmlinuz root=/dev/system/root resume=/dev/hda2 initrd /initrd Is there any necessity for a new default boot entry? Also note that the online update did not leave the previous kernel around, so any additional boot entry for a previous kernel would not help a bit in case the current kernel fails. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #53 from meissner@novell.com 2007-03-27 08:11 MST ------- We did test the update, just not under all possible conditions. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #54 from ma2412ma@hotmail.com 2007-03-28 00:59 MST ------- So you deliberately wanted to change the boot menu entry from "openSUSE 10.2" to "Kernel-2.6.18-whatever-blabla"? If so, bad choice. If not, you didn't thoroughly test (not only superficially), because this behavior can be seen on every Suse installation, it's not a special condition. So what about an update to this patch? Why does testing take so long _now_ ;-)? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #55 from kssingvo@novell.com 2007-03-28 03:47 MST ------- Hans Meier regarding Comment#54: sorry, but I have to disagree. I installed the patch now on 5 machines and noticed the issue 3 times. Still to much in my point of view, but not every SuSE installation. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #56 from judas_iscariote@shorewall.net 2007-03-28 03:58 MST -------
I installed the patch now on 5 machines and noticed the issue 3 times. Still to much in my point of view, but not every SuSE installation.
yes, the problem does not happend in 100% of the cases, also I dont think this bug is "critical" but only very ugly and annoying :-) if there is any "test fix" let us to know so we can test it ( Im not afraid of messing up my grub entries ;) ) ps: /me writting this from system with a borked grub menu but working perfectly :-) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #57 from suse-beta@cboltz.de 2007-04-02 14:41 MST ------- (In reply to comment #56)
also I dont think this bug is "critical" but only very ugly and annoying :-)
only ugly? IMHO this bug would also qualify as blocker - it makes systems with LILO probably unbootable :-/ (comment #36) That said: what's the status of the bugfix? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdan52@comcast.net ------- Comment #58 from judas_iscariote@shorewall.net 2007-04-02 20:41 MST ------- *** Bug 260109 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #59 from mike25@wanadoo.nl 2007-04-03 12:08 MST ------- Any news about the progress solving this annoying problem? maybe its handy to remove the kernel out of the repositories as well, untill this problem is fixed... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #60 from aosthof@novell.com 2007-04-04 01:04 MST ------- In reply to comment #54: The new name scheme will now look like "openSUSE 10.2 -- Kernel-2.6.18.8-0.1" for normal entries and "Failsafe -- Kernel-2.6.18.8-0.1" for failsafe kernel entries respectively. But this is only valid for grub, other bootloaders like lilo are limited in the length of such an entry. E.g. an entry for lilo will look like "oS_10.2". In general: A new package of perl-Bootloader (which caused the trouble) will be available these days for the community to get tested thoroughly. After about 2 weeks of testing, we'll release a new update kernel together with the new 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #61 from pley@alc.de 2007-04-13 07:23 MST ------- Hopefully I was the only one, who lost a partition because of this Bug: After upgrading the kernel and doing a suspend to disk, grub automatically started the first entry. That entry was another Linux system, which automatically mounted the suspended partition. :-/ I'd suggest you to hurry up to fix this. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #62 from aj@novell.com 2007-04-13 07:29 MST ------- We just released some packages for testing: http://lists.opensuse.org/opensuse/2007-04/msg01603.html We hope it's fixed - but we would rather have some more testers instead of breaking more stuff :-(. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #63 from alberto.passalacqua@tin.it 2007-04-13 10:51 MST ------- The update worked here on my laptop. The config is: Arch: i386 Partitions: swap | / | home (no logical) The new kernel entry was created, the failsafe one (I readded it after the last patch) was updated with the new name. The system is bootable :-) The only issue is related to the new naming convention. The "openSUSE - kernel name" string is too long and covers the countdown symbol. Btw, it's quite useless (and looks horrible in my opinion) to have the kernel version in the grub menu. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #64 from wknauf@hg-online.de 2007-04-13 16:00 MST ------- Will the patch repair the "broken" menu.lst ? Which means: will it replace the entry "Kernel-2.6.18.8-0.1-default" and restore the previous two entries "openSUSE 10.2" and "Failsafe -- openSUSE 10.2" ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #65 from meissner@novell.com 2007-04-13 16:14 MST ------- it will no repair broken menu.lst files. it might rename it to openSUSE 10.2 - kernel 2.6.18-8-0.2=-default or similar. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #66 from wknauf@hg-online.de 2007-04-13 16:18 MST ------- Would it be possible to restore the "Failsafe" entry if not found ? I was really glad I had it some time ago when the NVidia driver caused the normal system not to come up at all after a kernel update. Without it I probably would have had to reinstall the system. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #67 from judas_iscariote@shorewall.net 2007-04-13 16:25 MST ------- (In reply to comment #65)
it might rename it to openSUSE 10.2 - kernel 2.6.18-8-0.2=-default or similar.
The new naming convention is a brillant as the decision to intrdouce Zenworks into the distribution.. :-) ewwwww.. it is just horrible and confusing. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #68 from benji.weber@gmail.com 2007-04-13 16:30 MST ------- The good news: This new patch correctly sets the new kernel to default. (original patch makes my machine unbootable by selecting a kernel which doesn't boot as default in menu.lst) The bad news: The kernel version is appended to the distribution name now, which looks very ugly, and potentially confusing to users. "2.6.18.2-default" will mean absolutely nothing to most people. This text also overlaps the countdown timer which gives graphical glitches. To add to the confusion the existing entry simply named "openSUSE 10.2" is still there. Given the choice between "openSUSE 10.2" and "openSUSE 10.2 <random numbers here>" people might be confused and pick the "openSUSE 10.2" entry. In my opinion the default should be the distribution name as always before, and any older kernels should be labeled in a meaningful way like : openSUSE 10.2 openSUSE 10.2 [failsafe] openSUSE 10.2 [pre-update] If you really need /all/ the old ones listed (I imagine this would get interesting if you had more than 10 installed, does grub get a scrollbar :s) then I would think the date would be more meaningful than version. openSUSE 10.2 openSUSE 10.2 [failsafe] openSUSE 10.2 (2007-04-13 backup) openSUSE 10.2 (2007-03-15 backup) or similar. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #69 from jamesrome@alum.mit.edu 2007-04-13 16:41 MST ------- Yes, please be sure it restores the failsafe option. Mine are all gone, and I do not know how to restore them. I am not so concerned about the names. I understand the kernel version, and it would inform the user that the kernel had changed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #70 from aosthof@novell.com 2007-04-16 05:36 MST ------- Concerning the new naming scheme: As we don't want to use symlinks anymore - we want to be able to install and boot more than 2 kernels - we need unique names in the boot menu. So, if one has 3 different kernels installed for instance, the corresponding boot entries must be named in a unique way to be distinguishable. Therefore we use the new naming scheme with attached "Kernel-<release>". Concerning failsafe entries: With the new perl-Bootloader, if a kernel is updated or installed, a corresponding failsafe entry will be added, too (Note: only kernels with one of flavour smp/bigsmp/default will get an additional failsafe entry). I don't understand what's confusing if a <kernel-release> suffix is appended to the boot entry. Yet, I understand the (graphical) problem with the countdown timer. I'll try to fix this. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #71 from alberto.passalacqua@tin.it 2007-04-16 05:57 MST ------- The naming with the kernel versions is obscure and useless for many openSUSE users, who are not only Linux experts or geeks. Moreover it looks horrible. I agree with what Benjamin proposed (comment #68). Naming multiple kernels briefly and with clear names, indicating if it's a backup, xen or so should be more effective. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #72 from judas_iscariote@shorewall.net 2007-04-16 16:55 MST ------- (In reply to comment #70)
we want to be able to install and boot more than 2 kernels
who? have you ever asked the users ? - we need unique names in the boot menu. Yes, but please considere changing this, it looks very geeky and this is not slackware or debian, this is supposed to be an user friendly desktop oriented distribution. do not loose the focus!! you may need to do some extra work, but please think in the amount of silly questions we will have to answer due to this change. users have zero interest in the kernel release name, this new naming scheme is a benefit for a minority and a anooyance for the rest. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #73 from ma2412ma@hotmail.com 2007-04-17 00:30 MST ------- I absolutely agree with Cristian, Alberto, Benjamin (just about everyone) that appending the kernel version to the boot menu entry is a very bad idea from an ordinary user's perspective. If you really need to boot more than two kernels, comment #68 provides a sensible suggestion, the normal user doesn't need (or want) the technical details on which kernel version is being used. Please keep in mind who should be using openSUSE, and then imagine having to explain that cryptic number to your parents/grandparents/... who wonder what the hell has happened to their computer. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #74 from judas_iscariote@shorewall.net 2007-04-17 03:18 MST ------- (In reply to comment #68)
openSUSE 10.2 openSUSE 10.2 [failsafe] openSUSE 10.2 (2007-04-13 backup) openSUSE 10.2 (2007-03-15 backup)
or similar.
yes, this is a good idea, if people at novell still dont like it, you can add your obscure/geeky/useless/horrible naming after..dunno, 2 or 3 different kernels, the average user will not use more than 1 or 2 I guess. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rhg@marxmeier.com ------- Comment #75 from judas_iscariote@shorewall.net 2007-04-19 03:39 MST ------- *** Bug 266110 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 angellafuente@solid-rock-it.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |angellafuente@solid-rock-it.com ------- Comment #76 from angellafuente@solid-rock-it.com 2007-04-20 03:25 MST ------- Hi: I think this bug is the same? https://bugzilla.novell.com/show_bug.cgi?id=263116 Isn't it? I did the upgrade and system couldn't boot. :-( -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #77 from bjoern@cs.tu-berlin.de 2007-04-25 14:02 MST ------- After repairing the Grub and Lilo configuration for more around 15 openSUSE users, I think, the bug is a major problem. Also repairing boot loaders does not work without pain in current openSUSE: 1) the new graphical rescue system o the openSUSE boot CD/DVD was unable to write a working Lilo or Grub configuration (/dev/hda was reported as a RAID device, may be same cause like for 3) 2) there are no backups for /etc/lilo.conf 3) the manual rescue system is hard to manage, because users have to bind-mount the devices (mount /dev /mnt/dev -o bind), otherwise "lilo -r /mnt -C /etc/lilo.conf does not work because of missing /mnt/dev/* device nodes), it's documented in the openSUSE Start manual, but it's unknown for most users 4) Yast could not create a new configuration automatically (it created two incomplete entries) Isn't it possible to downgrade to an older (working) kernel update method for openSUSE 10.2 updates? In theory, I think it's a good idea, to allow, that multiple kernels can write entries in lilo.conf or menu.lst. But I also do not want to loose the old default entries like "openSUSE XX.X", "Failsafe" or "Shipped". By the way: Where are the vmlinuz.shipped entries? "vmlinuz.shipped" probably never worked as expected, because it was only a copy of the initial "vmlinuz" and "initrd" files. Bootings with "vmlinuz.shipped" caused problems because of missing modules in /lib/modules if the kernel was updated. But it would be really good for rescue purposes to have a working "vmlinuz.shipped" installation with all /lib/modules/"shipped" modules. Especially the option "Boot installed system" from the openSUSE installation CD/DVD would work like expected, if there is 100% compatible /lib/modules/"shipped" directory. My preferred Grub/Lilo configuration would like like: 1) * openSUSE 10.2 (which points to the latest /boot/vmlinuz link) 2) openSUSE 10.2 Failsafe (which points to the latest /boot/vmlinuz link) 3) openSUSE.shipped (which points to the initial installed kernel and refers to modules which are 100% compatible to the boot CD/DVD) 4) all other installed kernels 5) Memtest86 *) default -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #78 from alan.goodale@bmo.com 2007-04-25 21:05 MST ------- (In reply to comment #76)
Hi:
I think this bug is the same?
https://bugzilla.novell.com/show_bug.cgi?id=263116
Isn't it?
I did the upgrade and system couldn't boot. :-(
(In reply to comment #62)
We just released some packages for testing:
http://lists.opensuse.org/opensuse/2007-04/msg01603.html
We hope it's fixed - but we would rather have some more testers instead of breaking more stuff :-(.
I have tested the update (opensuse/2007-04/msg01603.html) by reinstalling from scratch, and then updating using the instructions provided. The patch has solved one of my problems (see bug # 263116). My system now boots after the kernel upgrade. However, I have several comments. 1) The menu entries for the previous version are gone, along with the previous version. It would have been nice to maintain this as a fall-back in case the update had problems - which it certainly did. 2) The new menu entries make no sense. The prospective target audience for SUSE Linux will be families and business people, not technicians. They don't care about things like "Kernel-2.6.18.8-0.2". It must be as understandable and straightforward as Windows - more so if possible. Anything else will scare people away. 3) Isn't the Failsafe selection supposed to boot into run level 3? The "3" is missing from my menu.lst file. 4) My original menu.lst file had a comment line before each of the title lines that began - ###Don't change this comment .... Those comment lines are all missing from the new entries that were added to the file. Only the entries for the Floppy and Windows still have comment lines. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 aosthof@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Group|SUSE Enterprise Partner | Component|Basesystem |Basesystem Product|SUSE Linux Enterprise Server|openSUSE 10.2 |10 SP1 | Version|Beta1 |Final ------- Comment #80 from aosthof@novell.com 2007-04-26 09:00 MST ------- Changing product back to openSUSE 10.2 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nnizar@novell.com ------- Comment #81 from judas_iscariote@shorewall.net 2007-04-30 15:12 MST ------- *** Bug 270024 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 ------- Comment #82 from meissner@novell.com 2007-05-03 08:50 MST ------- perl-Bootloader and kernel update approved now. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=252911 stefan.fent@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #83 from stefan.fent@novell.com 2007-05-04 01:16 MST ------- I'll close this bug now, as the new perl-Bootloader fixes most of the different issues. For the future, I'd suggest to open one bugreport / bug Eg. the discussion about how section labels should look like isn't critical, IMO. Here's what we fixed: - the entries look like: openSUSE 10.3 - 2.6.18.... Any other useful ideas welcome. (Using the date is as ugly as the kernel-version, but it doesn't even help the expert.) - the entries are prepended to the list - a Failsafe entry is created - mdRAID, DMRAID is working - the default is only changed if the new kernel has the same flavour as the removed one (means: if xen is default, it'll remain default unless a new xen-kernel is installed) If there are still open problems, please open new bug reports. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com