Hi,
On 18.10.2017 19:42, Michael Tremer wrote:
Did you compare image size after? Is that being influenced by the memory parameter?
For the records:
Current 'next', as in previous posting:
Buildtime 03:59:03
***SNIP*** -rw-r--r-- 1 root root 255029305 Oct 19 05:15 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz -rw-r--r-- 1 root root 80 Oct 19 05:26 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5 -rw-r--r-- 1 root root 252170425 Oct 19 05:19 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz -rw-r--r-- 1 root root 85 Oct 19 05:26 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5 -rw-r--r-- 1 root root 184549376 Oct 19 04:50 ipfire-2.19.i586-full-core115.iso -rw-r--r-- 1 root root 68 Oct 19 05:26 ipfire-2.19.i586-full-core115.iso.md5 -rw-r--r-- 1 root root 3522 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2 -rw-r--r-- 1 root root 82 Oct 19 05:26 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5 ***SNAP***
'xz' updated to '5.2.3', "optimized":
Build time 3:30:05 ***SNIP***-rw-r--r-- 1 root root 255172283 Oct 19 20:41 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz -rw-r--r-- 1 root root 80 Oct 19 20:54 ipfire-2.19.1gb-ext4.i586-full-core115.img.gz.md5 -rw-r--r-- 1 root root 252156393 Oct 19 20:45 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz -rw-r--r-- 1 root root 85 Oct 19 20:54 ipfire-2.19.1gb-ext4-scon.i586-full-core115.img.gz.md5 -rw-r--r-- 1 root root 175112192 Oct 19 20:14 ipfire-2.19.i586-full-core115.iso -rw-r--r-- 1 root root 68 Oct 19 20:54 ipfire-2.19.i586-full-core115.iso.md5 -rw-r--r-- 1 root root 3531 Oct 19 20:54 ipfire-2.19.xen.i586-downloader-core115.tar.bz2 -rw-r--r-- 1 root root 82 Oct 19 20:54 ipfire-2.19.xen.i586-downloader-core115.tar.bz2.md5 ***SNAP***
Looks interesting?
Best, Matthias