On Sat, Jan 06, 2001 at 11:19:39AM +0100, Tibor D. wrote: > And the problem with overwriting the old configfile isn't very nice, > just 1 lilo.conf.old isn't enough, maybe a first possibility would be > with "logrotate"? its not just not nice, its a policy violation. packages are *forbidden* from touching a locally configured conffile without first asking permission. perserving the original is not enough, the original must *not* be touched, moved, or molested in any way until permission is granted by the admin (policy section 4.7.3 paragraph 3). the only case where permission is not required is with dpkg's conffile handing where the md5sum proves that the conffile is unchanged from the one distributed in the previous package version. any package that modifies, deletes, moves, renames, mutilates or otherwise molests a locally modified conffile without first asking and getting affirmative permission from the admin should have a bug filed against it with no less then severity: serious. Configuration files are defined in policy section 4.7. lynx file:/usr/share/doc/debian-policy/policy.html/index.html (apt-get install debian-policy if you didn't install priority standard packages) -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgp9czRicgn3k.pgp
Description: PGP signature