Bug 309437

Summary:	Bootloader installation leaves old bootloader
Product:	[openSUSE] openSUSE 10.3	Reporter:	Michal Svec <msvec>
Component:	Installation	Assignee:	Stefan Fent <stefan.fent>
Status:	RESOLVED INVALID	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	duwe
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michal Svec 2007-09-11 09:40:01 UTC

I have two partitions, one with current stable release (10.2) the other with
new one (10.1 before, now 10.3b3).

I replaced old 10.1 with new 10.3b3 (new installation) and if I select 10.2
in the new bootloader configuration, it goes to the old bootloader menu, asking
for a choice again.

It's very confusing. Even more as the old menu contains broken items, specifically
10.1, which is no longer installed.

Comment 1 Torsten Duwe 2007-09-14 11:13:31 UTC


*** This bug has been marked as a duplicate of bug 309837 ***

Comment 2 Michal Svec 2007-09-19 13:46:18 UTC

Still the same behavior with RC1.

Comment 4 Stefan Fent 2007-10-24 19:33:32 UTC

works as designed, according to 
Fate #302302: switch bootloader configuration to chainloader/configfile

Comment 5 Michal Svec 2007-10-25 08:05:33 UTC

Sorry, but the design is broken then, if it leaves broken entries
in the bootloader menu.

Maybe we should revisit that feature again and/or implement some
reasonable behavior.

Comment 6 Stefan Fent 2007-10-25 08:49:10 UTC

No, we can't do anything about this.
It would be the same as if we required to change any other chainloaded systems boot menu, like windows, BSD - you imagine.

We can't change the menu of a different installation.

BTW, this probably wouldn't have hapened, if you hadn't changed the partitioning 
proposal, then your 10.1 would still be available.

If you have a good idea how to change this, feel free to open _a new_ FATE, as this one is done.