Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Vincent Danjean
On 18/06/2010 16:57, Petter Reinholdtsen wrote: [Thomas Hood] It is planned that an upcoming version of resolvconf will add a new hook script for isc-dhcp-client which is identical to the existing one for dhcp3-client. An administrator who has made local changes to the latter hook script

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Julien Cristau
On Sat, Jun 19, 2010 at 10:20:49 +0200, Vincent Danjean wrote: The difference here is that this is a copy, not a move, of the conffile. So you use cp instead of mv. Where's the problem exactly? Cheers, Julien signature.asc Description: Digital signature

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Petter Reinholdtsen
[Vincent Danjean] The difference here is that this is a copy, not a move, of the conffile. That is why I suggested to use a symlink too. This I would propose to move the conffile to the new location, and add a symlink in the old location to the new location, or just add a symlink to the old

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

2010-06-19 Thread Vincent Danjean
On 19/06/2010 10:44, Julien Cristau wrote: On Sat, Jun 19, 2010 at 10:20:49 +0200, Vincent Danjean wrote: The difference here is that this is a copy, not a move, of the conffile. So you use cp instead of mv. Where's the problem exactly? Should local modifications to the first script be