FreeBSD Handbook
Prev | Chapter 25 Updating and Upgrading FreeBSD | Next

# 25.8 Deleting Obsolete Files, Directories and Libraries

Based on notes provided by Anton Shterenlikht.

As a part of the FreeBSD development lifecycle, files and their contents occasionally become obsolete. This may be because functionality is implemented elsewhere, the version number of the library has changed, or it was removed from the system entirely. This includes old files, libraries, and directories, which should be removed when updating the system. The benefit is that the system is not cluttered with old files which take up unnecessary space on the storage and backup media. Additionally, if the old library has a security or stability issue, the system should be updated to the newer library to keep it safe and to prevent crashes caused by the old library. Files, directories, and libraries which are considered obsolete are listed in `/usr/src/ObsoleteFiles.inc`. The following instructions should be used to remove obsolete files during the system upgrade process.

Follow the steps outlined in Section 25.7.1. After the `make `installworld`` and the subsequent `mergemaster` have finished successfully, check for obsolete files and libraries as follows:

    # cd /usr/src
    # make check-old

If any obsolete files are found, they can be deleted using the following command:

    # make delete-old

> Tip: Refer to `/usr/src/Makefile` for more targets of interest.

A prompt is displayed before deleting each obsolete file. To skip the prompt and let the system remove these files automatically, use `BATCH_DELETE_OLD_FILES`:

    # make -DBATCH_DELETE_OLD_FILES delete-old

The same goal can be achieved by piping these commands through `yes`:

    # yes|make delete-old

> Warning: Deleting obsolete files will break applications that still depend on those obsolete files. This is especially true for old libraries. In most cases, the programs, ports, or libraries that used the old library need to be recompiled before `make `delete-old-libs`` is executed.

Utilities for checking shared library dependencies are available from the Ports Collection in `sysutils/libchk` or `sysutils/bsdadminscripts`.

Obsolete shared libraries can conflict with newer libraries, causing messages like these:

    /usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libtiff.so, may conflict with libz.so.5
    /usr/bin/ld: warning: librpcsvc.so.4, needed by /usr/local/lib/libXext.so, may conflict with librpcsvc.so.5

To solve these problems, determine which port installed the library:

    # pkg_info -W  /usr/local/lib/libtiff.so
    /usr/local/lib/libtiff.so was installed by package tiff-3.9.4
    # pkg_info -W /usr/local/lib/libXext.so
    /usr/local/lib/libXext.so was installed by package libXext-1.1.1,1

Then deinstall, rebuild and reinstall the port. `ports-mgmt/portmaster` can be used to automate this process. After all ports are rebuilt and no longer use the old libraries, delete the old libraries using the following command:

    # make delete-old-libs

Prev | Home | Next
Rebuilding “world” | Up | Tracking for Multiple Machines