From: Henrik.Carlqvist@deadspam.com   
      
   On Mon, 06 May 2024 08:20:33 -0400, Sam wrote:   
   > I sort of have a plan for my main servers, I track all of their   
   > configuration files and stash them in a git repo.   
      
   My plan for configuration files as well as custom software is to keep   
   them in custom Slackware packages. However, this is for those   
   configuration files intended to be shared among all, or at least several   
   machines. Examples of such files are ntpd.conf, sshd_config, snmpd.conf,   
   sendmail.cf and resolv.conf. For those few servers with a specific   
   purpose I store backups of their configuration file in a separate backed   
   up place, one directory for each server. Exemples of such files are   
   httpd.conf, exports, named.conf and slapd.conf.   
      
   By having those settings in custom Slackware packages I can quickly and   
   easily install an ordinary machine from scratch. Those specific servers   
   also have a backup plan for their configuration files. And when updating   
   ot a newer version of Slackware, I know exactly what configuration files   
   I have customized. I will most likely not be able to reuse all old   
   configuration files as is, but the tool kdiff3 or meld is great for those   
   situations as it with a quick glance show the differences between the new   
   stock configuration file, the old stock configuration file and my old   
   customized configuration file.   
      
   The biggest amount of time when upgrading to a newer version of Slackware   
   is to compile (ofter newer versions) of all those extra added software.   
   These days with slackbuilds.org and tools like slpkg that work is a lot   
   easier.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)