I think the root cause of the issue may be the conflation of two distinct properties: disk space occupied by the OS when installed, and the extra free disk space needed, over and above that, for it to install and then boot successfully. This second value is what is currently being "guessed" within ubiquity, with unfortunate results.
Therefore, perhaps we should have casper/filesystem.size represent the installed filesystem size for the installed distribution, and casper/filesystem.min-free-diskspace for the additional space needed. This would mean an end to the "fudge factor " approach in this ubiquity code, it would simply add the two values together to compute the minimum disk size needed for an install. If the second file is missing, fine, treat that value as zero (or even use a fudge factor, for improved backward compatibility?). Each flavour of Ubuntu would be responsible for creating an appropriate filesystem.min-free-diskspace file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784020 Title: ubiquity doubles stated filesystem size requirements -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
