lately, especially man pages around it but it's still very complex to get=2E even when i have tried to read confi= gs, manpages, makefiles, handbook etc=2E it feels like something is missing= =2E it's either in releng private repo or inside someone's brain=2E if in b= rain, those sometimes sadly expire and take all data with them, so=2E=2E=2E this comes from someone who installed 4=2E6 at age of 19 On April 15, 2026 1:52:42 PM GMT+03:00, vermaden w= rote: >> Adding it to your release configuration file has no effect=2E > >Colin did not wrote WHERE to put it - he just wrote this: > >> You want WITH_VMIMAGES=3DYES=2E > >=2E=2E=2E and I had that in release config=2E > >But contents of 'release=2Econf=2Esample' are useless and misleading=2E > >% grep -m 1 -B 2 WITH_VMIMAGES /usr/src/release/release=2Econf=2Esample >## Set to a non-empty value to build virtual machine images as part of th= e >## release build=2E >#WITH_VMIMAGES=3D > > > >> Second, `release=2Econf=3Dcustom=2Econf` has no effect either=2E > >I later moved to this =2E=2E=2E and it failed on build stage everytime in= different places: > ># =2E/release=2Esh -c build=2Econf > >=2E=2E=2E on system with 8 AMD Ryzen CPUs and 28 GB RAM and 200 GB of SSD= =2E > >But 'regular' command like that below worked without any problem: > ># make -j 8 buildworld buildkernel > > > >But all this is pointless now - I moved on to verimg(8) and I am more the= n happy with it=2E > > > > >