Minimizing the Installation
It is important to reduce the Sun Linux installation down to the minimum number of packages necessary to support the applications being hosted. This reduction in services, libraries, and applications helps increase security by reducing the number of subsystems that must be disabled, patched, and maintained.
Sun Linux uses RPM to install, upgrade, and delete packages. Each package maintains a description, file list, change log, checksum, and dependency information. Use this information to maintain and validate system integrity when adding, upgrading, or removing packages. To a limited degree, you can use the information to validate a package, before or after you install it on a system.
To remove an RPM package that is no longer needed, use the -e option with the rpm command, as in the following example:
# rpm -e minicom-2.00.0-3 # rpm -e glibc-2.2.5-42 error: removing these packages would break dependencies: glibc-common = 2.2.5-42 is needed by glibc-2.2.5-42
In the example, the first package minicom-2.00.0-3 is successfully removed. The second package glibc-common-2.2.5-42 is not removed, due to an unresolved package dependency.
When manipulating packages, take care to ensure that the RPM dependency tree is not inadvertently corrupted. We strongly recommend that you avoid using the options --force, --replacepkgs, --replacefiles and --oldpackage. Improper use of these options can cause the RPM dependency database to reflect an inaccurate state of a system.