| 1 |
On Sat, 4 Jan 2014 22:12:42 +0000 |
| 2 |
Neil Bothwick <neil@××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> On Sat, 4 Jan 2014 15:57:10 +0200, Gevisz wrote: |
| 5 |
> |
| 6 |
> > > etc-update or conf-update or similar |
| 7 |
> > |
| 8 |
> > I was afraid to run etc-update as man says it will replace |
| 9 |
> > everything automatically. However, I run dispatch-conf and it does |
| 10 |
> > not see any problems at /etc/ssh, which have only the following |
| 11 |
> > three files: moduli, ssh_config, sshd_config (though I have |
| 12 |
> > added /etc/ssh to CONFIG_PROTECT_MASK). |
| 13 |
> |
| 14 |
> Why did you do that? By masking out config file protection |
| 15 |
> for /etc/ssh there will never be anything to be managed by etc-update |
| 16 |
> as you have told portage to replace those files blindly and without |
| 17 |
> asking. |
| 18 |
|
| 19 |
From man "dispatch-conf": |
| 20 |
|
| 21 |
dispatch-conf will check all directories in the CONFIG_PROTECT |
| 22 |
variable. All config files found in CONFIG_PROTECT_MASK will |
| 23 |
automatically be updated for you by dispatch-conf. |
| 24 |
|
| 25 |
But anyway, |
| 26 |
|
| 27 |
1) I mask it only for one session, just to check that this does not help, |
| 28 |
|
| 29 |
2) as we have already figured out, there were no ssh config files |
| 30 |
to merge, only the dumb warning message issued without checking |
| 31 |
anything, and the latter, in my view, is a karma of ssh: it |
| 32 |
should have at least something implemented wrong :-) |
| 33 |
|
| 34 |
3) I will continue to do this job manually with gvimdiff as I have |
| 35 |
found it much more convenient than dispatch-conf (gvimdiff shows |
| 36 |
the differences a way much better). |
Archives