Re: [email@example.com: Re: why do we care about configuration files?]
>> On Fri, 18 Apr 2003 19:06:34 -0400,
>> David B Harris <firstname.lastname@example.org> said:
> if [[ "$always_yes" = "true" ]]; then
> grep -v '^/etc/foo/bar$' /etc/conffiles/managed > "$tempfile"
> && cp "$tempfile" /etc/conffiles/managed if ! grep
> '^/etc/foo/bar$' /etc/conffiles/unmanaged; then
> echo /etc/foo/bar >> /etc/conffiles/unmanaged
ucf development has something like this, except it is more
paranoid and checks to see if something is in managed and unmanaged
> But I dunno, the scenario I brought up would still remain. Even if a
> file is in /etc/conffiles/managed, the user still needs to be asked if
> it's okay to overwrite it, unless they tell the system otherwise.
Why? The only way a file would ever be lsited there is if the
admin put it there. I say that policy states that be default _no_
file goes into the managed list; and the shipped default for
/etc/coonffile/default is unmanahed. (managed is a list of files that
the package can freely over write).
> How will we let them tell it otherwise?
They told us that by entering a conffile name in the managed list.
> I'm thinking in the "may I upgrade your configuration file?" question,
> have the options I mentioned before ("no", "yes", "always-no").
> With "no" and "yes" being one-time-only things, "always-no" removing the
> line from /etc/conffiles/managed and adding it to
> How's that sound? It's unobtrusive, only adding a third option.
I think this is not needed. Since the shipped default is for
all files to be unmanaged, ie, not ever written over by default; any
files in the managed section were put in by explicit admin action.
Lost: gray and white female cat. Answers to electric can opener.
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C