On Wednesday, April 13, 2016 5:32:20 PM PDT Ancor Gonzalez Sosa wrote:
As you may know if you have followed previous blog posts by the YaST team, we are currently redesigning the YaST code for managing and proposing partitioning.
While designing the algorithm that proposes the disk layout for a new installation we came to a philosophical question - should we try to reuse existing swap partitions or should we always create our own?
If the current (i.e. old) installer finds a swap partition that is big enough for our needs, it will use it instead of creating a separate one. Although this can save some space, we are wondering if it's a good idea to do that by default. It effectively means that we will share the swap space with another Linux installation in the same computer. During normal operation that can be fine, but the swap partition is also used for suspend to disk (i.e. hibernate). That means that if we start LinuxA while LinuxB is hibernated, we will make impossible for LinuxB to resume the suspended execution.
Having separate swap partitions is safer from the hibernation point of view, but it consumes potentially valuable space just to make sure that you can run a Linux system while the other is hibernated, which can be considered a pretty weird scenario.
So, what the geckos out there think? Do you prefer to share swap partitions and save space or to have separate ones for better suspend isolation? Is there some implication or use-case that we have overlooked?
In any case, take into account that this will only be the proposed layout. You can always use expert partitioning to make your own.
Cheers.
I would recommend adding user-option for either keeping/creating, suggest keep for home user/single user and separate swap where security may be an issue. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org