4 ms·
Concept is interested, but read-only rootfs is stupid, really. It's kind of lock-in. Of course, ro - great for security, but if something happens with any crit
by paulcarroty 7y ago
Concept is interested, but read-only rootfs is stupid, really. It's kind of lock-in.
Of course, ro - great for security, but if something happens with any critical system component like bootloader - I prefer to able patch/fix it myself and don't wait days/weeks for distmakers.
Clear Linux use similar concept, but they allow write access and handle whole fs tree and bundle depends on server side.
- Jasper_ 7y agoIf you know how, there's an escape hatch. There are basically multiple filesystem trees under the hood (shared with hard links to avoid duplicating file data), and at boot time you'll get one of them. These are known as "OSTree deployments", and they're found in /ostree/deploy, and they're actually mutable, it's just the bind mounts into that location that are mounted RO. Anything in the bootloader configuration is not part of the deployment (from what I remember), and so it's mutable. See the docs here: https://ostree.readthedocs.io/en/latest/manual/deployment/ https://ostree.readthedocs.io/en/latest/manual/deployment/