On Wed, Sep 30, 2020, at 4:17 PM, Michael Catanzaro wrote:
On Wed, Sep 30, 2020 at 9:58 pm, Petr Menšík pemensik@redhat.com wrote:
Shouldn't it change resolv.conf only in case NM is active AND resolv.conf is generated by Network Manager?
Correct, that's indeed what it does. (Since Zbigniew changed it yesterday. Previously, it did not check if NM is active.)
I know this is already an epic thread but, just a FYI: This type of thing will completely not work on an rpm-ostree based system because the %post is run server side. It can't compute anything based on per-user data (and that's *also* true even when doing client side layering - the `/etc` that the `%post` script sees is the defaults, not anything a user has customized).
In general, any upgrade logic that needs to take into account user configuration needs to be a systemd unit, not a `%post`.