On Wed, Aug 21, 2002 at 03:00:52PM -0500, Steve Greenland wrote:
> On 21-Aug-02, 14:42 (CDT), Josip Rodin <[EMAIL PROTECTED]> wrote: 
> > On Wed, Aug 21, 2002 at 12:32:00PM -0700, Marc Singer wrote:
> > > How could it be dangerous to install a *missing* configuration file?
> > 
> > If the default configuration data in the file do something you don't want.
> > 
> 
> To be, perhaps, a little more explicit: there are programs for which
> the existence of an empty configuration file means something completely
> different than a missing a configuration file[1]. Thus, for dpkg
> conffile handling, removing a configuration file is a legitimate "edit".
> 

It would help to have an example.  However, even if there is an
example I don't see how db.root fits in this category.


Reply via email to