Bug 6003

Summary: Pre 2 Final - Rescue prefers mga1 system to mga2 when mounting partitions
Product: Mageia Reporter: claire robinson <eeeemail>
Component: Release (media or process)Assignee: Anne Nicolas <ennael1>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: sysadmin-bugs, thierry.vignaud, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakx-installer-rescue CVE:
Status comment:
Attachments: select "higher release number" root (mga first of course)
the same fix but step by step & commented

Description claire robinson 2012-05-21 11:31:59 CEST
Booting into rescue system and mounting partitions, it finds mga1 and mga2 but selects mga1 as rootfs. It seems like it should prefer an mga2 system over mga1.

http://dl.dropbox.com/u/4147101/Final/DSC01059.JPG
Manuel Hiebel 2012-05-21 12:36:44 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => drakx-installer-rescue

Comment 1 Thierry Vignaud 2012-05-21 14:46:50 CEST
Created attachment 2352 [details]
select "higher release number" root (mga first of course)
Comment 2 Thierry Vignaud 2012-05-21 14:51:38 CEST
We were just picking the first found mga system (so it depended on the partitions order).

For the record, in the old days, before favouring mga roots over mdv ones, we were taking the last one.

In both cases, it's arbitrary but still OK for most people who don't have several mga releases (physically) installed on the same machine.

We would need to interact with the user when there're more than one root and ask him to choose. (In MGA _3_)

In the mean time, this patch makes it select the mga root with the higher release number (if none, ditto for mdv roots).

Feel free to upload a patched drakx-installer-recue
Comment 3 Thierry Vignaud 2012-05-21 14:55:26 CEST
Created attachment 2354 [details]
the same fix but step by step & commented
Comment 4 Thomas Backlund 2012-05-21 15:04:38 CEST
(In reply to comment #3)
> Created attachment 2354 [details]
> the same fix but step by step & commented

Applied and pushed to bs

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED