https://bugzilla.novell.com/show_bug.cgi?id=223246 ------- Comment #2 from holgi@novell.com 2006-11-22 08:35 MST ------- But there is no way back if you once started this system ... Right, it is for multiple systems but not just 10.2 but also later systems. So if we do start such a 'solution' now the problems will pop up later ... but they will pop up -- 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=223246 holgi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|stefan.fent@novell.com |aj@novell.com ------- Comment #6 from holgi@novell.com 2006-11-27 04:49 MST -------

- Keeping the symlinks in menu.lst is not an option. The requirement to have one bootloader entry per kernel contradicts with the old "one and only vmlinux" entry paradigm.

What is the description for that - why is it not an option any more?

- #300543 is the most important FATE here, please also check the various references: #232, #2154, #301204 ...

fate #300543 tells: Whenever an additional kernel is installed, a unique bootloader entry must be created, and the bootloader has to be reinitialized, if necessary. I just read _additional_ kernel here but the problem is the standard/main (how do you want to call it?) kernel. If you do update the kernel of such a multi kernel system, which one will be updated?

- flawless support of multiboot setup, was never a supported feature as to my knowledge.

Strange: so we do we still generate these entries then?

- the work-around here would be to use various configfiles and/or chainloader stages instead of directly adressing the images for other systems directly. Unfortunately that work-around does not work for all architectures/ bootloaders. Else I would say, please file a feature request for that.

From my point of view: If you change part of the boot mechanism that causes problems on the other hand the better way would be to change the whole boot mechanism (add chainloader entries instead of current vmlinuz/initrd entries of other SUSE partitions). But as it is now - it's just done half of it.

- so the bottom line from my personal point of view is that this does not block anything except a nice but unsupported attribute of former distros and that an easy work-around exists.

What I'm wondering about: how many users do want to have multiple kernel support not knowing how to modify a grub entry comparing to how many users cannot but their other linux partition later not having the knoledge how to change the grub entry and are helpless. Nevertheless, it seems AJ have to decide about that here -- 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=223246 ihno@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ihno@novell.com |ke@novell.com Severity|Blocker |Major Component|YaST2 |YaST2 Product|openSUSE 10.2 |openSUSE 10.3 Version|RC 1 |Alpha 1 ------- Comment #8 from ihno@novell.com 2006-11-27 09:20 MST ------- This will not get fixed for 10.2 (too late). A different solution can be made in 10.3. The following snipped should be added to the Release Notes: ================================================ If multiple instances of openSuSE 10.2 are installed on one machine and the instance in partition 2 is booted from the grub in partition 1 the entry in menu.lst in partition 1 for partition 2 should contain the entry: kernel /boot/vmlinuz initrd /boot/initrd instead of kernel /boot/vmlinuz-2.6.18.2-23-default initrd /boot/initrd-2.6.18.2-23-default With this change it is safe to make a kernel update in partition 2 and the system can still be booted from partition 1. =================================================== -- 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=223246 ------- Comment #9 from holgi@novell.com 2006-11-27 09:37 MST ------- Ihno: What about the update problems? -- 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=223246 ------- Comment #11 from ihno@novell.com 2006-11-29 07:51 MST ------- @Holger: Thats what the snipped in comment #8 is for. -- 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=223246 odabrunz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #13 from odabrunz@novell.com 2007-02-02 10:39 MST ------- A different solution for later needs to be discussed. It should be there for 10.3, so that a 10.3 can still boot a installed 10.2. Some approaches are: - use a chainloader to load other installation, whereever a chainloader is available - in grub it is possible to load a different menu list At some point, but likely not for 10.3, it may be possible to have a two-stage boot scheme on all platforms. First stage loads the boot menu of an installation, the second stage loads the selected kernel there. (As we have it on IA64). For this we need to open a discussion in FATE. Leaving this bug open as a reminder until we have a FATE. -- 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=223246#c15 --- Comment #15 from Holger Sickenberg 2007-08-28 08:23:52 MST --- ping -- 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.