On Mon, Jan 24, 2005 at 04:23:40PM +1100, Taryn East wrote: > now I don't remember ever editing any of these (apart from crontab) so I > don't know what changed so I hit no to all of them...
You can hit 'd' to show what the changes between the two versions are. Very handy, since I have the same problem you do -- "I changed that file? I don't think so, let's have a look..." > but I'm pretty sure some of them could have easily been replaced without > being a problem - and maybe it would have been a good idea to just > install them anyway. Any file which the system is fairly certain you haven't changed are automatically updated. > however, now I'm not sure which files they were or how to update them - > is there any way to be able to tell which files are not the latest? > (I've tried just running dist-upgrade again, but that doesn't do > anything more. 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. - Matt
signature.asc
Description: Digital signature
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
