Val Packett 🧉<p><a href="https://social.treehouse.systems/tags/ParticleOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ParticleOS</span></a> (finally, <a href="https://social.treehouse.systems/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a>/linux) is a really cool idea in many ways but I absolutely can't stand fixed-size, fixed-number (2, a/b) hard partitioning for the OS images. What is this, Android? idk how to explain it without sounding like the TempleOS guy or something but fixed allocation of storage is literally like, spiritually offensive to me.</p><p>Why not at least leverage LVM to have flexible partitions, so that installing a new image would create a logical volume to write the erofs to? And have systemd-homed use logical volumes for homedirs too instead of files on a root fs? At least only <em>one</em> inflexibility would be left (homedir sizes, and even there: ext is shrinkable as scary as that operation sounds). If we're going the partition-ish route, I would prefer the root to not be an FS at all, but a flat thing like LVM that can flexibly contain system images and home dirs.</p><p>On the other hand why not only have the one single rootfs and drop the erofs images into it? and then homedirs could be either luks images (and the root is "flat" with only images inside), or fscrypt dirs (if you like me vastly prefer the flexibility to "omg gotta hide the <em>shape</em> of the fs tree too").</p><p>Of course AerynOS/moss is the genius solution that provides atomicity without images :p but I do appreciate the "do interesting stuff based on existing distros" thing. AerynOS doesn't have non-amd64 arches so far, and quickly putting together an image based system out of an existing aarch64 distro would've been great for me right now..</p>