https://bugzilla.novell.com/show_bug.cgi?id=779527
https://bugzilla.novell.com/show_bug.cgi?id=779527#c5
--- Comment #5 from Holger Arnold
The situation that installation is started from a live cd is not specially covered currently.
Normal installation do not have swap activated except for two reasons: 1) linuxrc activated it before starting yast because of low memory 2) the user itself activated it for some reason
I don't know for sure, but I think the installer (on the live CD) also uses existing swap partitions when started directly from the boot menu.
Deactivating all swap on start of partitioner seems to be too harsh. It potentially needs a long time and could make low mem systems hang almost forever. Mostly people will reuse their swap or create an additional swap in unused space (to be able to suspend multiple systems independently).
So I would assume the case of removal of a swap partition is quite rare.
On what data do you base your opinion? At least for me, this is not a rare use case. I think that the user should be able to change his disk layout exactly as he wants it, and active swap partitions prevent this. There is no point in having a powerful partitioning program, such as Yast's, and not being able to use it properly. Note that the same problem occurs with automatic disk partitioning. For example, what about a (novice) user that has an existing swap partition that is too small for suspending to disk? The partitioning algorithm would reuse the swap partition and use all remaining disk space for / and /home. The result would be that the user can't suspend his system! I think the best solution would be to ask the user when a swap partition has to be disabled to create a -- automatically or manually -- generated disk layout. The wording can be made beginner-friendly, such as: "If you do not know what this means, click 'Yes'." -- 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.