1 |
On Thursday, 30 May 2019 12:28:41 BST Dale wrote: |
2 |
|
3 |
> I use the dispatch one because it is better. No matter what I attempt |
4 |
> tho, I can not figure out how to use that dang merge thing. I wish |
5 |
> there was a GUI tool to do this. Maybe that would help. Of course, |
6 |
> someone will likely post that there is a GUI tool and then I'll wonder |
7 |
> how I missed it. ROFL You can bet I'd use it tho. |
8 |
|
9 |
There's also cfg-update and there may be more tools to manage changes in |
10 |
config files following an update. |
11 |
|
12 |
The merge function is particularly useful, because you can see where your |
13 |
edits are/not affected by any changes to the new config defaults and reject/ |
14 |
accept one change at a time. |
15 |
|
16 |
You can define what tool will be used for diff-ing in the /etc/dispatch- |
17 |
conf.conf file, or equivalent. I use colordiff, but I supposed you could set |
18 |
up meld, kompare, or some other GUI file comparison application to be launched. |
19 |
|
20 |
With colordiff once you press 'm' to merge changes, you get your existing |
21 |
config file shown on the left and the changed config on the right. Pressing |
22 |
'l' retains your existing config, 'r' overwrites yours with the new defaults. |
23 |
When you finish it asks if you want to overwrite the existing config with the |
24 |
newly merged file. Up until this moment you can choose to cancel all changes |
25 |
and the old config file will be retained as it was. |
26 |
|
27 |
Overwriten config files are archived in /etc/config-archive, so you can always |
28 |
revert any changes you made by mistake. |
29 |
|
30 |
HTH. |
31 |
-- |
32 |
Regards, |
33 |
Mick |