> I use Silverblue. How does this affect my ability to modify /etc in the > opt-in scenario? Does rpm-ostree offer a method to modify /etc in that > case? What if I want a mutable /var, like I currently have, does this > change under this proposal? What is the value of this for the normal > Fedora Linux user? Note that this is only about `/sysroot`, not `/` (root). Thus `/etc` and `var` are still writable in all cases. > I don't know. I think not being able to boot into my previous > deployments a visible change to my user experience. Once the new option has been set, you will have to append `rw` to the kernel command line to previous deployments that were created before. We could also probably make this even more conservative and have it only enabled once all your deployments have the new kernel option. This should avoid the case where you can not bee an older deployment anymore. The idea is to make the update happen in two steps: - First add the `rw` kernel arguments, - Then set up the `sysroot.readonly` option once all previous deployments have the rw option. -- Timothée Ravier CoreOS engineer & Fedora Kinoite maintainer _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
