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 :
>
>> On 24/02/2020 11:52, Martin Gregorie wrote:
>>> However, it did teach me a lesson, which is that its a very
>>> good idea to make a copy of every file you change in /etc and its
>>> subdirectories and keep the copies in one of your normal login user.
>>
>> 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.
>>
>> ---druck
>
> 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.
---druck
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|