worth noting that because of the constraints of the setup you can develop something similar on your main machine without any realistic possibility of data loss since you never really touch the bootloader or the filesystem (partitioning and so on).
worth noting that because of the constraints of the setup you can develop something similar on your main machine without any realistic possibility of data loss since you never really touch the bootloader or the filesystem (partitioning and so on).
okanat•2h ago
For example, it is quite annoying to have a sane font setup due to Arch shipping vanilla. Fontconfig sucks, it has bad documentation and Arch Wiki examples go only so far. Among the entire distro universe only Fedora has sane configs. So an immutable Arch goes against immutability.
Moreover OSTree requires a server to receive updates regularly, are you going to put the effort to building the OSTree multiple times a day? Why should we trust a single person?
mxxc•1h ago
smashed•1h ago
I could see someone wanting to build an arch based firmware with OTA updates use this as a proof of concept. Yes, they would have to customize it and operate some infra but that does not make it useless.
mxxc•46m ago
i must say that even though this tech has been around for a while it's still very much WIP. much of the ostree command line is undocumented, some commands are hidden and even though there is significant overlap between rpm-ostree, ostree and bootc, they do quite different things and some things are easy with one tool and outright impossible with the other. but personally i think this is the future of "mainstream" linux, and even though "immutable linux" has been often associated to locked platforms (e.g. android), it's been fun to showcase how you can do it yourself too, with whichever distro you like.