![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2022-09-12 05:54, David T-G wrote:
Hi, all --
...
in my own .vimrc file, but that doesn't seem to matter ...
This concept has come up before for default aliases, too. I tried a few ways to permanently stomp on some /etc/profile.d/* files, but anything that promises to be permanent also breaks updates, so I'm stuck making the same changes again and again. I foresee the same thing with syntax settings *sigh*
It should not break updates. When there is an update to those files, one of two things can happen: 1) Your file is replaced with a new file, but actually it is renamed to /path/someconfig.rpmorig 2) Your file remains intact, but the update appears renamed to /path/someconfig.rpmnew It is your job as administrator to check for the existence of those files. There is a command that list them: Telcontar:~ # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/apparmor.d/usr.sbin.smbd.rpmnew /etc/rsyslog.d/remote.conf.rpmnew /etc/smartd_warning.sh.rpmnew /etc/zypp/zypp.conf.rpmnew Telcontar:~ # Telcontar:~ # l /etc/zypp/zypp.conf.rpmnew /etc/zypp/zypp.conf -rw-r--r-- 1 root root 21865 Jan 13 2021 /etc/zypp/zypp.conf -rw-r--r-- 1 root root 21547 Feb 3 2022 /etc/zypp/zypp.conf.rpmnew Telcontar:~ # So now I would do: meld /etc/zypp/zypp.conf.rpmnew /etc/zypp/zypp.conf and check the changes to accept them or not. Finally: rm /etc/zypp/zypp.conf.rpmnew Usually, I do a backup of both files before doing any change. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)