Unpacking of installation file
To start custom installation, unpack the installation file <file_name>.run without starting product installation. For that, use --noexec command-line parameter:
# ./<file_name>.run --noexec
After the command execution, <file_name> subdirectory appears in the current directory.
Moreover, you can use the following command-line parameters with the installation file:
--keep - create <file_name> directory containing setup files, in the current directory (not in /tmp), and do not delete it after completion of installation.
--target <path_to_dir> - create <file_name> directory containing setup files, in the specified directory. Note that this directory will automatically be deleted after completion of installation, if you do not specify also the --keep or --noexec command-line parameter.
To see full list of available command-line parameters allowed for the installation file, execute the command
$ ./<file_name>.run --help
Custom installation of components
The created subdirectory is an installation directory that contains auxiliary files and all component packages included in Dr.Web for Linux. Each <component_name> component package contains two files: <component_name>.install and <component_name>.remove. These files are command scripts. The first script is used for package installation and the second script performs package removal. Names of all packages containing Dr.Web for Linux components start with "drweb" prefix.
To install a certain component, run the appropriate installation file in the console (or console emulator, which is a terminal for graphics mode).
When installing any of the product components, dependencies are supported; that is, if component installation requires other components, they are checked to be present in the system and, if not, they are installed automatically.
If it is necessary to start the full product installation, launch the installation script from the extracted directory. For that, use the following command: