How to deal with overloaded config files?

[jsch]

Hello


Some system-tools (e.g. udev, eg25-manager, ...) allow you to overload the configuration by placing a changed version below `/etc`. As long as the package maintainer does not adjust the original configuration this works fine. If the config is changed and you are not aware of that, your systems might behave "strange" (it no longer does the things you expect).
What is the best way to keep track of changes in config files where a cloned config was created?

My attempt is reflected in the attached file.
  check_config_diffs.txt (Size: 2.31 KB / Downloads: 128)

[treebeard]

Hello


Some system-tools (e.g. udev, eg25-manager, ...) allow you to overload the configuration by placing a changed version below `/etc`. As long as the package maintainer does not adjust the original configuration this works fine. If the config is changed and you are not aware of that, your systems might behave "strange" (it no longer does the things you expect).
What is the best way to keep track of changes in config files where a cloned config was created?

My attempt is reflected in the attached file.

Mobian seems to have the ucf package installed by default so I think anytime a changed config file is replaced during an upgrade the old one gets renamed with a certain extension.  After any upgrade I do
```
sudo find / -xdev -name "*.dpkg-*"
sudo find / -xdev -name "*.ucf-*"
```
to find the replacements.  I can do a diff between old and new to see what changed and then do whatever is needed to resolve.