4 ms·
a) Not all programs can read multiple configuration files. It's either in the one configuration file or a hardcoded default. b) Not all settings done in defaul
by jlg23 6y ago
a) Not all programs can read multiple configuration files. It's either in the one configuration file or a hardcoded default.
b) Not all settings done in defaults can be simply undone later on (e.g.: apache's httpd.conf, IIRC the same for nginx - good luck getting this default listener down again)
c) If you want to infer which changes were made by you or by the system's update procedures, explicitly creating snapshots before every manual or automatic modifications would be the way to go. Preferably one after each as well, so you have something to verify the integrity of a system against in case of security issues.
- zaarn 6y agoa) and b) are just issues with common software being idiotic about configuration and insisting one a "one truth" central config file. c) As mentioned above, inferring changes requires two snapshots, if /etc only contains changes a single snapshot allows me to infer changes. And I can verify the integrity just as well using an "after" snapshot. Just means one less snapshot is involved, which is reduced complexity.