On Wed, 2005-01-26 at 14:56 +1100, [EMAIL PROTECTED] wrote: > On 24 Jan, Matthew Palmer wrote: > > When the system handles one of these "conflicts", a new file will be > > created > > -- either <conffile>.dpkg-new (if you chose to keep your version) or > > <conffile>.dpkg-old (if you chose to replace your version). So, you can > > easily find all files you decided not to replace by a command like this: > > > > find /etc -name \*.dpkg-new > > > > And then go and have a look at them all and decide if you want to manually > > replace them or not. > > If you're running apt on an rpm-based system, then the packages will be > called things like *.rpmsave or *.rpmnew.
The two are similar but slightly different. Normally an upgraded package won't overwrite your existing config file. In this case, the new file gets a .rpmnew extension. If the new config file must be used, say because of added/removed settings, then the old file is backed up with a .rpmsave extension, and then replaced with the new file. -- Pete -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
