DdB wrote: > 3. The simplistic approach: > To get to that goal, i did create a directory purely to hold the > status of my changes in the following form. For every modification > to the system, i considered being worth keeping, i stored 3 files. > 1. the original file as Ubuntu had installed it. > 2. a "Pointer" (a file containing the path to the location of that > file), and also some description of the initial problem and my > workaround. Later, this was as useful as a piece of documentation. > 3. the modified file which had made my life easier. > Furthermore, i made a simple script to check, if my "solution" was > still in place. Later, i allowed this script to restore my solution > automatically, if it found the situation being unchanged relative to > the beginning of my work.
Excellent, You have independently re-invented the work of many sysadmins over the last 25 years! The system you have constructed is a kind of configuration management tool. Existing tools like this include salt, ansible, puppet, chef, bcfg, cfengine, and more specialized things like vagrant (largely used to construct virtual machines) and Nix (as NixOS, attempts to define an entire Linux distribution through a repeatable program). You can see that re-inventing this approach is very popular. Since many of these tools are already packaged for Debian, I assure you that, in my opinion, discussing your tool is fully on-topic here. -dsr-
