How does Silverblue handle new defaults?

We can see here how Fedora Workstation handles configuration files when an update brings new default configurations with it.
How does Silverblue do it instead? As far as I know it stores the default config of the associated deployment the associated /usr/etc and then it just calculates the new /etc folder?
Is there a way to know if a package has new defaults and update the config file? Something like rpmconf for workstation?

Does Silverblue have better capabilites at adapting to the new defaults of a release?

1 Like

Silverblue (or more specifically, libostree) will update config files on update if they haven’t been modified. You can use ostree admin config-diff to see modified config files. See Atomic Upgrades - ostreedev/ostree for more details.

1 Like