On Sun, Oct 15, 2006 at 09:06:40AM +0200, Bo ?rsted Andresen wrote
> I suspect you don't really understand what CONFIG_PROTECT{,_MASK} is. Please
> read the output of `emerge --help --config`. All the files you've mentioned
> are covered by CONFIG_PROTECT in a default configuration so if they aren't it
> means you've screwed up your CONFIG_PROTECT and/or CONFIG_PROTECT_MASK
> variables. Otherwise it is you who overwrote those files with
> etc-update/dispatch-conf or whatever you use for that.
Maybe I didn't make myself clear enough. It works as designed. I did
not overwrite the files, but I'm getting annoyed at having to tell
etc-update "NO" every few weeks when I run etc-update. There are
anywhere from 10 to 40 files to plow through. And I have a 7-year-old
PIII Dell as my emergency backup machine, so I repeat the process all
over again.
What worries me is that one of these days I'll hit the wrong key (Y
instead of N) and zap a config file. Yes, I do have backups, but how
long will it take me to realize what's happened? What I'm asking for is
a way to pre-emptively tell etc-update not to bother me about certain
files. Zap the new version and keep the old.
--
Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1
My musings on technology and security at http://techsec.blog.ca
--
gentoo-user@gentoo.org mailing list
