> Booting from ZFS seemed like a hassle, without clear benefits.
I'm running ZFS on a single boot/user partition on an XPS 13 (9370.) I was unable to get the built in WiFi working with Debian Stretch but it seems to work well enough with testing (Buster.) I have apt-buglist and apt-listchanges (or similar) installed to warn me of possible problems, but I feel more comfortable thinking that I can roll back a system that becomes borked by a buggy upgrade. (Haven't had to do it yet.) Ordinarily I'd have a separate $HOME partition but I'm settling on a $HOME filesystem (which is covered by `rsync` backups.)
It was a bit of a hassle but not IMO w/out benefits for my use case.
I have other servers running Debian Stretch and Ubuntu 16.04 that are using ZFS on the storage drives/partitions and EXT4 on the root partition. (These are for personal use.)
I'm running ZFS on a single boot/user partition on an XPS 13 (9370.) I was unable to get the built in WiFi working with Debian Stretch but it seems to work well enough with testing (Buster.) I have apt-buglist and apt-listchanges (or similar) installed to warn me of possible problems, but I feel more comfortable thinking that I can roll back a system that becomes borked by a buggy upgrade. (Haven't had to do it yet.) Ordinarily I'd have a separate $HOME partition but I'm settling on a $HOME filesystem (which is covered by `rsync` backups.)
It was a bit of a hassle but not IMO w/out benefits for my use case.
I have other servers running Debian Stretch and Ubuntu 16.04 that are using ZFS on the storage drives/partitions and EXT4 on the root partition. (These are for personal use.)