On Thursday 01 September 2005 04:09 am, Neil Bothwick wrote:
On Wed, 31 Aug 2005 20:16:55 -0700, Mark Knecht wrote:
2) If it's a file in /etc/initd then I update it automatically.
This rule is still true. I am not a programmer and will never edit
an init script. For me these are 100%
On Wed, 31 Aug 2005 20:16:55 -0700, Mark Knecht wrote:
2) If it's a file in /etc/initd then I update it automatically.
This rule is still true. I am not a programmer and will never edit an
init script. For me these are 100% updated ASAP.
Add /etc/init.d to CONFIG_PROTECT_MASK in
On Tue, 30 Aug 2005 17:19:40 -0400, Sean Higgins wrote:
It exists as an option with dispatch-conf, as do options to
automatically replace files if the only differences are whitespace
and comments.
But, it does not automatically do an update if the original file has
not changed. That
Thanks everyone for your help. I will try using Marks rules and start
using dispatch-conf to be able to roll back any changes that don't seem
to work.
Jerry
Mark Knecht wrote:
On 8/30/05, Jerry Turba [EMAIL PROTECTED] wrote:
As I understand the process etc-update lists new configuration
On 8/31/05, Jerry Turba [EMAIL PROTECTED] wrote:
Thanks everyone for your help. I will try using Marks rules and start
using dispatch-conf to be able to roll back any changes that don't seem
to work.
Jerry
Darn, that's scary! OK, if you're gonna follow someone as blind as me
le me expand
As I understand the process etc-update lists new configuration files
provided by the program authors. I have tried to define some rules for
myself to determine how to handle these new files.
1. If I made a change to a file I will never allow the new config file
to overwrite the old file.
2.
On 8/30/05, Jerry Turba [EMAIL PROTECTED] wrote:
As I understand the process etc-update lists new configuration files
provided by the program authors. I have tried to define some rules for
myself to determine how to handle these new files.
1. If I made a change to a file I will never allow
On 30/08/05, Jerry Turba [EMAIL PROTECTED] wrote:
As I understand the process etc-update lists new configuration files
provided by the program authors. I have tried to define some rules for
myself to determine how to handle these new files.
1. If I made a change to a file I will never allow
Jerry Turba schreef:
As I understand the process etc-update lists new configuration files
provided by the program authors. I have tried to define some rules for
myself to determine how to handle these new files.
1. If I made a change to a file I will never allow the new config file
to
On Tue, 2005-08-30 at 16:46 +0200, Holly Bostick wrote:
Jerry Turba schreef:
As I understand the process etc-update lists new configuration files
provided by the program authors. I have tried to define some rules for
myself to determine how to handle these new files.
1. If I made a
On Tue, 30 Aug 2005 12:06:29 -0400, Eric Crossman wrote:
While I agree that etc-update is a vast improvement over other package
systems, it would be nice to have a CVS type merge where I only have to
make choices when the system can't figure it out. It seems like
etc-update (and friends)
On Tuesday 30 August 2005 01:22 pm, Neil Bothwick wrote:
On Tue, 30 Aug 2005 12:06:29 -0400, Eric Crossman wrote:
While I agree that etc-update is a vast improvement over other package
systems, it would be nice to have a CVS type merge where I only have to
make choices when the system can't
12 matches
Mail list logo
