I'll never stop emphasizing how underrated mfsBSD is and how convenient it can be. This morning, I had to set up a FreeBSD server on an OVH machine. The remote console wasn't cooperating when trying to attach an ISO, and it was performing poorly (I'll open a ticket about it when I find the time). Thanks to mfsBSD, I swiftly installed FreeBSD 13.2, but when I attempted to upgrade to 14.0 and update ZFS, it wouldn't boot anymore. In just five minutes, I prepared an mfsBSD image with FreeBSD 14.0 (not yet available on the official site) and got everything up and running. Such a handy tool that has saved me from unpleasant situations countless times.
@solobsd@kta@stefano there is a strong use case for this for micro sd booted devices (like pi systems) given the poor long term write reuse, and performance, of sd micro drives.
@kta@solobsd@stefano the pi 3 was the last one I could still reliably depend on passively cooled. Because I only cared about headless applications that may have to run for many years much of what happened, even with the pi 3, let alone after, was kinda useless to me.
@gnutelephony@solobsd@stefano -- yeah, absolutely. I was thinking of buying a stack of refurbished optiplex micro form factor machines and have them netboot off an image. And have them collaborate on CPU/RAM intensive work with Dask. Could do this with RPIs, but when buying in bulk, you might get more CPU/ram/$ with a bunch of micro form factor machines. https://www.freshports.org/devel/py-distributed/https://a.co/d/2AQfifg
@kta@solobsd@stefano I wonder if solobsd would be a good match for use cases I liked Alpine Linux for (Alpine also has a pure boot to ramdisk rootfs operating mode). Can I build up a collection of custom ports packages and make them easily part of a solobsd system at boot?