I’d prefer not to create different topic for each question I have - it would feel like spam for me , so I hope you forgive me listing them in single thread.
Q1.Explanatory (background) story.
I did a test measuring average boot times for various Linux, FreeBSD and Windows operating systems, all on the more-or-less same hardware (for some test-OS I HAD to switch graphics card). Machine had SATA SSD.
Took me most of the day but it yielded some interesting results. I noticed that TrueOS had ~35sec (35,64) boot time against vanilla FreeBSD’s ~15 (15,04) seconds. Exact numbers varied a bit and I took arithmetic average of multiple boots. FreeBSD install ran SLiM/XFCE4 combo on ZFS - not exact copy of what TrueOS would run but I wanted something easy to compare against Linux distros as well (especially against Alpine, which is also one Linux distro using OpenRC init - but it is musl-based and XFCE4 was only non-console option for it).
I noticed that majority of time went into “getting the kernel going” for TrueOS. Once OpenRC started doing it’s bit - boot became fast. Looking at it bit more closely I saw BUNCH (close to 50) of drivers were loaded up. Many of them totally unasked for. Example. I did not have wifi module in machine but for some reason - bunch of the wifi drivers had been loaded up. Which I think caused most of the time difference compared to vanilla FreeBSD.
I took time-out and installed PC-BSD 10.3 and found something similar. But I also found how and from where the loaded drivers were “called” from.check out line 135 for example
Now the question: Exactly where in TrueOS I could “adjust” the list of drivers being loaded boot-time? It’s obviously no longer in /etc/rc.conf.pcbsd , /etc/rc.conf.trueos nor could I find anything which could trigger it from /boot
Q2 How would I install TrueOS on a drive with a MBR partitioning scheme AND have it boot successfully?
I have Acer Aspire 5560 laptop. It has idiotic broken Phoenix UEFI bios implementation which does not allow installing anything besides Windows using UEFI. And even then it does not work properly - once you have deleted original Acer partitioning layout and “lost” recovery partition from it. Which I had, because original drive simply died and I put in replacement.
In Bios - no option for manual “legacy boot”. It seems to decide “which way to go” based purely on what partitioning scheme is on the disk.
Attempting to EFI boot TrueOS (and FreeBSD) ends up with a “kernel trap 12” message. Linux boot medias would just freeze. FreeBSD MBR install works just fine.
I used to do “manual install” using UFS2 file system on a MBR-formatted disk on this laptop but seems like this “terminal window option” for advanced installs is by now gone from more TrueOS installers.
Just selecting MBR install from “advanced” installer options would install the TrueOS but upon reboot all I would get would be # marks in boot loader. Any advice?
GRUB2 seems not to work with the ZFS. Would legacy GRUB be an option?
Q3 What’s the state of Lazarus and fpc in TrueOS ports? Do they work fine? If not, what problems have you been running into?