Hello fedi! I'm making my own immutable distro, and I've got some questions:

• what should I use to build? I was thinking bluebuild hut it might be more trouble than it saves, as I need to do stuff like add an extra btrfs subvolume on install, and I'd like a custom gtk4 installer.
• other than that, assuming I use bluebuild for now, would a structure like this work?
• core - has core system stuff, like kernel, bootloader, etc. Included in image, needs reboot to apply
• other/system - has other stuff like system flatpaks, config files, anything that doesn't need a reboot to change
  Each would be cached so only core or other would be rebuilt depending on the last value.
• other would use an overlay inside a btrfs sub volume. I was thinking I apply changes directly to the subvolume and rollback if they interrupt or an error occurs, but now I'm thinking a power cut or other force shutdown might mess that up.

Any thoughts would be appreciated, thanks! You're helping to shape QuadOS! QuadOS currently has the following devs: Me, @Heliguy, and @winsdominoes. It aims to be like NixOS, but using flatpaks, and hopefully less janky.

#distro #linux #immutable #immutableOS #quadOS