On Wed, Aug 26, 2020 at 4:06 AM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
My suggestion would be that if the install process could detect/know that it is below the limits
needed it would notify the user and not proceed. That is, not just crash.
Knowing memory requirements in advance for an ever-changing codebase across different system architectures. If you can find a solution, you might win some prize and recognition in the theoretical informatics field ;-)
The best that we could possibly do is to regularly test all the different types of images on different architectures, find a reasonable lower limit, and then hardcode the limit in anaconda (which would need to reliably detect the environment it is running in) and inform the user if the free memory is too low (not just total memory, because the user can start a few programs in the live environment before starting the installer, and you suddenly have much less memory available). Repeat the testing at least once per cycle, ideally multiple times. If that sounds like a lot of work, it sounds correct. That's why a note in the system requirements section on the download page is usually how everybody deals with this.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
