Is what you want explicitly 'config' files, or is it a list of any files
which have been modified from the distribution version? Would comparing
checksums with the original files do the trick? Presumably there's not
much need to back up config scripts which are known to be unchanged from
the originally distributed version.
Depending on the system, you can get local configuration stuff worked into
a lot of places the package maintainer may not have expected. Sometimes
the configuration files don't cover everything you need to customise and
you wind up doctoring a script or something of the sort.
I haven't used these, but debsums or dlocate might do what you need for
comparing checksums.
Restoring all modified files could have a downside of course in the event
that you are recovering after a security compromise. You could wind up
recovering exactly the thing you're trying to eradicate by restoring from
backup.
Andrew
On Mon, 28 Jul 2003, Peter Chubb wrote:
Hi,
I'm trying to set up a backup strategy. What I want to find
is all the configuration files for the various installed packages.
Some are obvious (/etc/apache/http.d.conf, /etc/passwd) Others are not
(/usr/lib/python2.2/site-packages/MoinMoin/config.py).
Is there a way of extracting from the dpkg information a list of all
changed configuration files? Dpkg must know this info...
Peter C
--
No added Sugar. Not tested on animals. May contain traces of Nuts. If
irritation occurs, discontinue use.
---
Andrew McNaughton In Sydney
Working on a Product Recommender System
[EMAIL PROTECTED]
Mobile: +61 422 753 792 http://staff.scoop.co.nz/andrew/cv.doc
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
