© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There's not really any good way around this. The default behavior in the old Ubiquity installer was (IIRC):
* Don't create a swapfile by default when doing manual partitioning.
* Create a swapfile by default for any other installation mode.
With Calamares, we only have two options that aren't the same as this behavior:
* Always create swap unless using Erase Disk mode and the user explicitly turns it off
OR
* Never create swap unless using Erase Disk mode and the user explicitly turns it on
Both of these are different from Ubiquity's behavior. Going with "never create swap" has slightly more danger than going with "always create swap", and it has a higher chance of confusing a user who's used to Ubiquity.
At some point (perhaps for the OO cycle), we should try and get in a feature that allows the user to customize which filesystem they want the swapfile to be on, like wxl mentioned. That would be my favorite solution, though it's too late to try it for this cycle.
In the short term, we may need to just release note this bug and try to fix it via an SRU to add some notice that a swapfile is being created on the Summary screen, or disable swapfile creation when using manual partitioning (both options that wxl covered above).