On Thu, 2022-12-08 at 20:23 +0100, drago01 wrote: > > Please bear in mind the difference between bare metal and virtual > > machines. The bare metal machine may have 32 GB of RAM, making a > > 800 MB install image a non-issue. For a public cloud virtual > > machine > > though, this could bump your VM sizing up 1 level from 2 GB quota > > to a 4 GB RAM quota, with correspondingly higher price point. Now > > most people probably don't run the installer in a public cloud, > > preferring pre-built disk images. Even in a local machine though, > > you may be using most of your 32 GB of RAM for other things (well > > firefox/chrome), so allowing extra for the VM is not without > > resource cost. If we could figure out a way to knock a few 100 MB > > off the installer RAM requirements that is valuable. > > > > > The problem I see here is not the presence of the firmware on the > image, > but the fact that it seems to be loaded into memory despite not being > used. This is the direction Daniel was thinking down. I'm waiting for someone with more expertise to reply, but I suspect the reply is going to be along the lines of "yes, we *can* do that, but it's somewhat tricky work that involves thinking about lots of paths that aren't obvious, and somebody would need to dedicate their time to working on that". -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
