alis VS systemrescue-zfs

IMHO, it still lacks proper error handling. When i'm in a hurry, i usually end up using ALIS. https://picodotdev.github.io/alis/

have a look at ALIS by picodot. https://github.com/picodotdev/alis

No, it's like any other distribution. Even installation is now simplified through scripts like alis (https://picodotdev.github.io/alis/).

I like arch and I use alis to install it using systemd and xfce. There's no ide you need to manually edit the conf file and hope you didnt do anything it didnt like https://picodotdev.github.io/alis/

Suppose if I want to fit this os and all necessary app dependencies on a smart toaster or fridge... but maintain absolute stability and reasonable response metrics. Bare metal through full capability deployment is what I'm thinking with Linux auto install, similar to https://github.com/khuedoan/homelab or https://github.com/picodotdev/alis

Sorry I can't help but I wanted to say I was able to manually set up my partition using parted on the arch installer and this script allowed me to choose the boot and root partition https://github.com/picodotdev/alis

Arch. I prefer using an install script for the first part of customization https://github.com/picodotdev/alis

There's a rescue system here with zfs support pre installed: https://github.com/nchevsky/systemrescue-zfs/tags

It looks like the boot-pool on the original SSDs just got flat out destroyed when installing the new copy on the usb stick. I used this recovery image from here: https://github.com/nchevsky/systemrescue-zfs/releases and booted the system with all disks installed. 'zdb -e boot-pool' spit out a load of unneeded stuff and a list of the most recent zpool commands run on the pool. What do you say, zpool destroy was the last command run on it at the time of the usb installation... One 'zpool import -Df boot-pool' later the pool was visible again. 'zpool export boot-pool' and a reboot later the system once again boots into the original install.