On 28/02/2020 11:39, Jan Panteltje wrote:
> On a sunny day (Thu, 27 Feb 2020 20:56:16 +0000) it happened druck
>  wrote in :
>
>> On 27/02/2020 05:38, Jan Panteltje wrote:
>>> On a sunny day (Wed, 26 Feb 2020 20:33:07 +0000) it happened druck
>>>  wrote in :
>>>> Even better, install the etckeeper package. This will store all changes
>>>> to files in etc in git repository. When you edit a file, you can either
>>>> manually commit it with a comment explaining what you have done, or if
>>>> you forget it will automatically commit them on a daily cron task. It
>>>> also detects changes made by the package manager, so its easy to find
>>>> out what happened if things go wrong.
>>>
>>> Even better, backup everything on a regular basis
>>
>> No, the above isn't about backups, its change management. If something
>> stopped working because of a change to a file in /etc which happened
>> several months ago, will you still have a backup of that file, and how
>> many backups will you have to go through to find that change? Using etc
>> keeper you have a log of every change to the file, so you can identify
>> he breaking change, and either revert it either in whole or part.
>
> I have backups of the whole system every so many days.

[Snip]
>
> What I do editing config files is make a copy
> cp xxxconfig xxxconfig.org
> and then rewrite it

I'm sure your disc is a completely logical arrangement of

xxxconfig
xxxconfig.org
xxxconfig.org1
xxxconfig.org2
xxxconfig.org3
xxxconfig.org4
xxxconfig.old
xxxconfig.old4
xxxconfig.bak
xxxconfig.bak2011
xxxconfig.orig
xxxconfig.dist
xxxconfig.kept
xxxconfig.temp
xxxconfig.working

You probably dont even have to diff every one of them to work out what
changed each time.

---druck

--- SoupGate-Win32 v1.05