On Sun, Jul 09, 2006 at 05:29:06PM +0200, Alexander Skwar wrote > Gerhard Hoogterp schrieb: > >> When I say "yes" I mean "yes". When I say "no" I mean "no". And I > >>don't mean "just until the next update" either. I have reasons for my > >>settings; please don't act like Windows and assume that you know better > >>than me. And there is no excuse whatsoever for wiping out the custom > >>settings in /etc/conf.d/local.start > > > >As I wrote in an other mail: Stop interfering with the actual configfile > >and add the changes to a config.conf.dist file. > > Yep, you wrote that, and I answered that *I* would *NOT* like this. > I like it, that I can use a program right away - at least in a > "default" way. If you had your way, *NO* program which relied on > configuration files would be usable after installation, as no > configuration file could be found. Because of that, I would not want > to happen what you proposed.
I think there's a mis-understanding here. Gerhard and I are complaining about config files being possibly *OVERWRITTEN* with default settings. If there's no config file, sure write the default config file. But if someone has customized a config file, assume that they know what they're doing, and leave settings alone. -- Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
