Bug 5982 - Installer asks to reboot when the installation is not finished (modifications of partitions)
Summary: Installer asks to reboot when the installation is not finished (modifications...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-19 20:25 CEST by Simple
Modified: 2014-11-17 16:16 CET (History)
0 users

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:


Attachments

Description Simple 2012-05-19 20:25:31 CEST
Run Mageia 2 installer and in partitioning step, i did add and removed some partitions, i was trying to understand why in the installer you can change the LVM partition type in advanced mode.
Anyway at some point the installer said:

You need to reboot before the modifications take effect.

how can this be possible if the installation has not even started installing packages, this is only one of the steps of the installation process, doesnt make much sense.
Comment 1 Manuel Hiebel 2012-05-19 20:43:20 CEST
it is so since some years, even if you remove/deleted/create new partitions

Source RPM: (none) => drakx-installer-stage2

Comment 2 Marja Van Waes 2012-05-26 13:09:30 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Simple 2012-05-27 04:19:11 CEST

Keywords: NEEDINFO => (none)

Manuel Hiebel 2012-05-27 14:28:02 CEST

Summary: Installer asks to reboot when the instalation is not finished => Installer asks to reboot when the installation is not finished (modifications of partitions)

Comment 3 Dick Gevers 2014-11-17 16:16:07 CET
As Manuel already explained, this is the way the system works (diskdrake). 

IMHO it is only natural that a certain number of partitioning steps need to be completed before it can continue.

Therefor, I believe the only 'solution' is "wontfix". 

Anyone who disagrees may reopen the bug, though.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.