Thanks for your feedbacks guys
Something that immediately had my attention in the FreeBSD installer was a wpa_tui prompt to establish a wireless connection right from the installer. That was great user experience to be honest, something that has always bothered me in the Linux world: networking while installing
Adelie has a good result with bcnm program, i will see if i can get the same result for Obarun.
First hiccup: The guided partitioning is awesome! BUT: There was no mentioning of whether or not the disk was mounted after the formatting. Since I didn't recall the development phase on this I thought I'd rather exit the script to make sure I have the disk mounted in any case and to my surprise it got mounted by the script. This is really great but it needs a short informational message that this happened
maybe a recap of what it did can be good
First bug: Apparently I chose to EFISTUB install, as always, and, again to my surprise, I got asked if I wanted to install microcode. I chose to do so but then there was no further choice to be made. This led me to believe that the script had some logic to find my CPU manufacturer. Something along the lines of lspci | grep "Host bridge" or whatever. Well it turns out the script does nothing at all. It neither downloaded any microcode package nor did it add an initramfs entry to the EFI entry. So I had to rewrite the entry manually afterwards and also chroot to install the microcode package
i need to investigate this
Second hiccup: While in chroot I decided to add labels to the partitions, as I always do. This is non-destructive for regular partitions, but as far as my practice goes, Swap space can not get labelled without being recreated. This led to it getting a new UUID and my fresh install not boot after finishing the script. Had to become aware of this and manually edit fstab. This was not at all the fault of the script, just posting this users experience here
this is a very case and you go over the script installation. I don't see what i can do for that.
Side note on EFISTUB: resume=UUID=SWAP-UUID could/should(?) be automatically written when Swap was chosen before as one does not consider this a "custom kernel parameter" I'd think. Also the microcode part of initramfs=\amd-ucode.img could/should(?) be put before initramfs=\initramfs-linux.img by the script if microcode was chosen as this also would not be considered a "custom" kernel parameter by most. In both cases maybe another line needs to explain this when prompting for custom parameters: "Do you want to add custom kernel parameters? We already included RESUME and microcode INITRAMFS parameters according to your choices." I hope I explain myself here
you're right, again i need to investigate this.
People complain about this installer:"So much complex", so "Stop to ask me to incorporate features" :p.
I'm kidding here