Created attachment 755 [details] report.bug of this install Same as bug 1371, only different distribution (1 vs 1rc) Installer checks the box before the worst option, when showing the possibilities for install: to use the <1GB partition after the rescue partition of a Lenovo Thinkpad SL510 This problem only occurs repeatedly on this Thinkpad, but not on other Lenovo/IBM systems I tried.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=1371Source RPM: (none) => drakx-installer-stage2-13.58
Summary: installer choses a partition smaller than 1 GB to install Mageia => installer chooses a partition smaller than 1 GB to install Mageia
Attachment 755 mime type: application/octet-stream => text/plain
I think it is indeed the designed behaviour (if there is free space, use it as it is safer than resizing another partition) I don't see how to improve that (I often install on partitions under 1GB in VMs so they should not be ignored)
CC: (none) => pterjan
I was only trying to think as a first-time Linux-user, who would probably not dare to make a different choice from what installer proposes and would consequently end up with nothing. I didn't know what you said about installing in VMs (I don't use VM's), you're right that that should be taken into account. If you want to close this bug, that's fine with me.
Well I have never seen a machine with a small empty partition so far, usually either the full disk is used when you buy the machine or you add an empty disk. But we should find a better way to handle it (but I don't know how, I would need to think more about it)
There wasn't a small empty partition on it when I bought it, there was only some empty space on the restore partition and that was turned into a seperate empty partition when I installed mageia rc on it.
I'm glad that you want to think about it, does that mean this bug can be assigned to you?
Yes sorry, I meant a small empty space :) Usually existing partitions cover all disk.
Assignee: bugsquad => pterjan
I think I was wrong to open this report. * Although the triage guide says the same bug for a different release, should be filed again against that different release, it is useless to do that here, because installer bugs can only be solved for the next release. So adding a comment in the original report that it is still valid for a newer release, would have been enough. * Although this report is slightly different than bug 1371, because here the small space is an empty partition, this is in fact the same bug because this small empty partition was created when bug 1371 happened. Closing as invalid @ pterjan Feel free to reopen if you disagree
Status: NEW => RESOLVEDResolution: (none) => INVALID