Do we need to update system config files after an upgrade?

General
1

On regular Fedora, after a major upgrade there is an optional step to update system configuration files. What what I know of Bluefin the “/etc” directory is still fairly mutable. So should we also be doing this step after Bluefin upgrades?

Most configuration files are stored in the /etc folder. If you have changed the package’s configuration files, RPM creates new files with either .rpmnew (the new default config file), or .rpmsave (your old config file backed up). You can search for these files, or use the rpmconf tool that simplifies this process.

2

Do “rpmnew” and “rpmsave” files even get generated when we upgrade on Bluefin, or does it just work differently?

3

You don’t need to do any of this.

4

Yup, as Jorge said, you really dont need to do any of that, but the system will not tell you that something is different than the image default. You can check this by using ujust check-local-overrides and checking your files on etc.

2 Likes
5

That is only in fact if you never touched the default config. Let me give you an example.

On bluefin there is a file called ublue-update.toml, which I have someday edited to change the min_battery_percent value.

~ ❯ cat /etc/ublue-update/ublue-update.toml
[checks]
    min_battery_percent = 50.0
    max_cpu_load_percent = 50.0
    max_mem_percent = 90.0
[notify]
    dbus_notify = false

Because I have changed this file, it will never get updated to a new version. So when I look at the upstream provided version of this file.

~ ❯ cat /usr/etc/ublue-update/ublue-update.toml 
[checks]
    min_battery_percent = 20.0
    max_cpu_load_percent = 50.0
    max_mem_percent = 90.0
    network_not_metered = true  # Abort if network connection is metered
[notify]
    dbus_notify = false

As you can see, there is now an option provided that it won’t check on metered connections.

So in my case it will always default to the default network_not_metered of the application because it can’t read the value in my config file. So it can be useful to check your modified config files from time to time.

This command can help you with that

sudo ostree admin config-diff
.....
M    ublue-update/ublue-update.toml
......

You ofcourse see alot of other files that are modified, but not by you intentionally. But I think this file was a great example to show.

This link below gives you a little more information, it tells you about the config file part.

Nice, all this in a just command, I’ve learned a new one today. Thanks! :smile:

4 Likes