Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Rich Freeman <rich0@g.o>
Subject: Re: Re: RFC: Enable FEATURES=config-protect-if-modified by default?
Date: Wed, 16 May 2012 06:51:00 -0400
On Wed, May 16, 2012 at 5:02 AM, Fabio Erculiani <lxnay@g.o> wrote:
> I implemented this feature in Entropy long time ago (2009 iirc) and
> enabled it by default as well.
> We never had a single issue. Users seem quite happy about it.
>

This is also the default behavior with the cfg-update alternative to
dispatch-conf - unmodified files are just replaced.  Never had a
problem with it.  90% of the time these are files I've never even
looked at.

Will the new option remove files automatically as well?  I've been
getting warnings on boot that I suspect are the result of ancient udev
rules files that never got removed due to protection.  I've been
meaning to investigate, but I need to figure out which if any I did
actually modify.

Rich


References:
RFC: Enable FEATURES=config-protect-if-modified by default?
-- Zac Medico
Re: Re: RFC: Enable FEATURES=config-protect-if-modified by default?
-- Fabio Erculiani
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: RFC: Enable FEATURES=config-protect-if-modified by default?
Next by thread:
Re: Re: RFC: Enable FEATURES=config-protect-if-modified by default?
Previous by date:
Re: Re: RFC: Enable FEATURES=config-protect-if-modified by default?
Next by date:
Re: [gentoo-dev-announce] Lastrite: 4suite, amara and testoob (mostly for security)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.