03:48:40 <rmustacc> Someone in here a while back was asking about DIMM temp sensors over i2c where there wasn't a bmc on the scene right?
06:19:58 <wiedi> yes I was
09:24:39 <stefanobsdcafe> Hello. You may like this: https://it-notes.dragas.net/2025/09/19/freebsd-vs-smartos-whos-faster-for-jails-zones-bhyve/
19:24:50 <darwin> want to install Illumos (Tribblox, OmniOS CE) on my new PC.  Had trouble installing more than one on old PC maybe due to ZFS naming.  If I just name partitions/filesystems for each OS instead of naming one root and installing each within two parts then no problem... or do I need to make one 'root' with two parts?
19:25:22 <richlowe> in general terms, virtualization is so much better than multi booting
19:26:27 <richlowe> in specifics, I don't know if you can have two functioning root _pools_ (tsoome? do you know?) but you _can_ put pretty much anything in a BE rootfs
19:27:44 <darwin> yeah, I guess I couldn't name them the same... but I can name them different and still use as roots, maybe?
19:28:57 <darwin> i prefer multi-booting.  Emulators/virtual_machines have their own problems
19:29:20 <darwin> i multi-boot and chroot because it's generally easy, and if one OS has serious problems, I can boot right into another... and I have the space
19:56:15 <tsoome> richlowe you can, but with small tricks; one thing is that if you want them to be totally independent, you would need to manually manage bootloaders a bit; with BIOS boot, the gptzfsboot is read from pool boot blocks, but you need to get to load partition boot block somehow (pmbr does not provide prompt and only supports one partition to boot from). loader64.efi gets partition LBA recorded in it, but is stored in ESP/efi/boot, so you would
19:56:15 <tsoome>  need to move it into alternate location and configure EFI boot manager.
19:57:50 <tsoome> or, you can use single boot loader and add other pool into primary pool/boot/menu.lst,  either in form of alternate BE or via chainload.
19:58:49 <tsoome> menu.lst(5) has few examples
20:03:03 <jclulow_> "loader64.efi gets partition LBA recorded in it" does it?!
20:07:41 <tsoome> yes, installboot does it via multiboot structure. it is not ideal, but till there is no secure boot support, it does suffice.  the reason is obvious - if you have multiple pools on the disk, it has no way to know where to load the kernel from.  fbsd opts to use first pool it can find. The alternative solution would be to use config file from ESP, but at the time, I did decide to use same mechanism as with BIOS version.
20:12:09 <tsoome> if there is no LBA recorded (value is 0), it does pick up first pool it can find and does have /boot/defaults/loader.conf in its bootfs.