Salix Forums

Recently i tried (but didn't find it handy) amavisd. After uninstalling i saw, that in /etc there were still the config files and even in /etc/rc.d the rc.amavisd file. In slackware, the uninstall just uninstalls only the binaries but does not kill the related config files etc.?

If so, is there a tool or script or somewhat other more elegant way to delete those orphaned files than doing a systemwide search with catfish?

TIA.

Certain files in /etc have a .new extension. When installing a package that you haven't previously installed, the .new suffix is automaticaly removed. These are configuration files that you don't want an upgrade to replace the existing file though. So when you're upgrading a package, if the file (without the .new suffix) is already there, it won't be replaced. It's up to the user to check the .new file and see if any changes need to be made to his own configuration file. We have a tool for that: dotnew (and dotnew-gtk).

The package info includes entries for the .new files, but not without the .new. So these will stay there after uninstallation. If you remove from a terminal, you'll see messages that spkg couldn't find the .new file to remove. You can remove these manually (or not, they just take up a tiny amount of space).

Slackware and slackbuilds sadly install /etc/rc.d/rc.* files, which are not configuration files, as .new files. Salix packages don't do that, but it's impossible to change that in packages that are coming from slackware.

Thanks for the info!