On Wed, Feb 16, 2022, at 12:48 PM, Stephen Snow wrote:
On Wed, 2022-02-16 at 12:12 -0500, Ben Cotton wrote:
>
https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot
>
> == Summary ==
>
> This change is about enabling an opt-in ostree feature that re-mounts
> `/sysroot` as read only to avoid accidental changes.
>
> Users and administrators are not expected to directly interact with
> the content available there and should instead use the interface
> offered by rpm-ostree, GNOME Software or (soon) Plasma Discover to
> manage their system.
>
I use Silverblue. How does this affect my ability to modify /etc in the
opt-in scenario?
It doesn't; `/etc` is mounted writable.
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?
`/var` does not change either.
What is the value of this for the normal Fedora Linux user?
The basic idea is that `/sysroot` is actually an ostree implementation detail, and really
nothing else should be writing to it.
Fedora CoreOS has worked this way for a long time; we just didn't make the change in
ostree by default out of conservatism.
See, that's an unwelcome thing IMO.
I think actually the migration service could inject `rw` into all bootloader entries
actually.
I don't know. I think not being able to boot into my previous
deployments a visible change to my user experience.
The service adjusting all bootloader entries is the easy fix for this.
Or, TL;DR: Don't panic, no power is being removed and it's very likely that no one
will notice.