On Wednesday 2016-09-07 14:34, Ludwig Nussel wrote:
Carlos E. R. schrieb:
I understand you want to try several installations with different memory ammounts, right? Which ammounts? I already know that 3/4 a GB
You have to try how low you can go. The lowest amount possible is when the boot loader can't load kernel and initrd anymore or linuxrc crashes at startup. When linuxrc or YaST start but crash later, passing values for the above mentioned parameters should make linuxrc create swap and allow to continue the installation. Maybe Steffen can has some hints how to find out how to tune MemLimit, MemLoadImage and MemYaST?
makes the net install to fail, yast processes get killed, but works with the full dvd install in graphics mode.
Perhaps a table of tests to do?
Yes, a table could help to visualize the result.
BTW, we worked on reducing the install memory footprint recently: https://lizards.opensuse.org/2016/07/27/highlights-of-yast-development-sprin... For this I collected some numbers (see attached file). The things mentioned there have all been implemented meanwhile. You can see that tumbleweed (I would place leap close to tw) needs more space than sles12 but not _that_ much more. And as sles12 _does_ install on 0.5 GB machines, it's not clear why 0.75 GB should be a problem for leap. Even if you account for larger repositories. It is true that there are hooks still in linuxrc for quite some counter-measures including activating swap and even creating a swap file on a windows partition (haven't tried this for a decade but the code is still there...). But the memory limits for those haven't been updated for ages. Mainly because it is a bit unpractical: you have to tune them again for every release and every architecture. And yes, it changes from beta to beta. So, basically we've given up on the fine-tuning and just say 'go for 1GB'. That said, I think that leap failing to install on 0.75 GB would be a bug. Steffen