Rootdisk checks

Several file checks are performed when building the rootdisk. These checks are done by the kreatv-finalize-rootdisk IIP before creating the rootdisk archive file.

Finding unstripped binaries

If unstripped files (files containing debug symbols) are found, they are listed under the warning message Warning: unstripped files found on rootdisk.

Symbolic links using absolute paths

Symbolic links in the rootdisk should be relative. If symlinks using absolute paths are found, a warning message is printed.

Finding unused or missing shared libraries

The rootdisk is searched for shared libraries (.so files) that are not used by any executables or other shared libraries. A search is also performed for executables that depend on libraries that are missing in the rootdisk.

Most errors found by this mechanism are caused by IIPs that include too many or too few libraries. However, there are cases when this mechanism cannot know that a library is used, for example when plugins are loaded with dlopen. There are a couple of methods to cope with that situation:

Marking plugin directories

Plugins are often compiled as shared libraries and loaded in runtime with dlopen(). Directories containing plugins should have a file named .plugindir, created by the IIP that uses the plugins. Those directories are skipped when looking for unused libraries.

Whitelisting unused library files

Shared library files can be marked as used by adding an empty file with the name of the library with .usedfile appended (for example libsomething.so.7.usedfile). The library is then skipped when looking for unused libraries.

Whitelisting missing library files

Missing shared library files can be ignored by adding an empty file with the name of the library with .ignoremissing appended (for example libsomething.so.7.ignoremissing). The library is then considered present on the rootdisk when looking for missing libraries.