I'm in the process of configuring a remote machine. But my experience tells me that it's hard to keep track of all the changes that I made to the machine.
So I decided to write a script that stores all my original *.conf files in a separate directory rather than my previous practice of making a .bak file in the current directory.
Now I'm wondering... what are the pros and cons for softlinking the config files to actual config files in a separate directory?
For example, /etc/fstab is a soft link to /etc/custom/fstab
The original fstab is stored as /etc/custom/original/fstab
And any changes that I make are in the /etc/custom/fstab
Recent copies of custom config files are stored in /ets.custom/backup
The script is gonna be quite elaborate, but once done I think it's gonna safe me a lot of trouble. But as you might imagine, I am not completely sure of the implications of soft linking any custom configs.
EDIT: This script will work equally well for working with different versions of scripts and plain text files. Maybe the /etc/ directory isn't the most sane place to store backups and originals then... but that is just one variable to adjust.