Custom Installation and Uninstallation of Components |
In this section •Typical Component Sets for Custom Installation •Installation and Uninstallation of Dr.Web Security Space Components Installed from a Repository oUnpacking the Installation File oCustom Installation of Components oCustom Uninstallation of Components If necessary, you can choose to install or uninstall only certain Dr.Web Security Space components by installing or uninstalling the respective packages. Perform custom installation or uninstallation the same way Dr.Web Security Space was installed. To reinstall a component, you can uninstall it first and then install again. Typical Component Sets for Custom Installation If you need to install Dr.Web Security Space with limited functionality, you can install only component packages that provide the necessary functionality instead of installing a root meta-package from the repository or from the universal package. The packages required to resolve dependencies will be automatically installed. The table below displays component sets designed to resolve typical Dr.Web Security Space tasks. The Packages for Installation column lists packages required for installation to obtain the specified component set.
Installation and Uninstallation of Dr.Web Security Space Components Installed from a Repository If Dr.Web Security Space is installed from a repository, to install or uninstall a component, use a respective command of the package manager of your OS, for example: 1.To remove the Dr.Web Network Checker component (the drweb-netcheck package) from Dr.Web Security Space installed on CentOS, use the command:
2.To add the Dr.Web Network Checker component (the drweb-netcheck package) to Dr.Web Security Space installed on Ubuntu, use the command:
If necessary, use help on the package manager of your OS. Installation and Uninstallation of Dr.Web Security Space Components Installed from a Universal Package If Dr.Web Security Space is installed from a universal package and you want to additionally install or reinstall a package of a component, you will need an installation file (with the .run extension) that was used to install Dr.Web Security Space. If you do not have this file anymore, download it from the Doctor Web company website. Unpacking the Installation File When you start the .run file, you can specify the following command-line parameters: --noexec—unpack Dr.Web Security Space installation files instead of starting the installation process; --keep—do not delete Dr.Web Security Space installation files and the installation log after the installation; --target <directory>—unpack Dr.Web Security Space installation files to the specified <directory>. To get a full list of command-line parameters that can be used with the installation file, run the command:
For custom installation of Dr.Web Security Space components, unpack the contents of the installation file. To do that, run the command:
Custom Installation of Components The .run installation file contains packages of all Dr.Web Security Space components (in the RPM format) and auxiliary files. Package files of each component are named as follows:
where <version> is a string that contains the version and date of a package release, and <platform> is a platform to run Dr.Web Security Space. Names of all Dr.Web Security Space component packages start with the drweb prefix. The installation kit includes the zypper package manager intended for the installation of packages. For custom installation, use the installpkg.sh service script. To do that, firstly unpack the contents of the installation package to any writeable directory.
To install a component package, go to the directory containing the unpacked installation file and run the command from the command line or from a terminal emulator:
For example:
If it is necessary to install Dr.Web Security Space in full, start the installation script by running the command:
Furthermore, you can install all Dr.Web Security Space packages (among other things, to install missing or accidentally removed components) by starting the installation of the root meta-package:
Custom Uninstallation of Components If your OS uses RPM packages, to uninstall a package of a component, use the corresponding uninstallation command of the package manager of your OS: •on Red Hat Enterprise Linux and CentOS, use the yum remove <package_name> command; •on Fedora, use the yum remove <package_name> or dnf remove <package_name> command; •on SUSE Linux, use the zypper remove <package_name> command; •on Mageia or OpenMandriva Lx, use the urpme <package_name> command; •on ALT, use the apt-get remove <package_name> command. For example, on Red Hat Enterprise Linux:
If your OS uses DEB packages, or there is no package manager in your system, for the custom uninstallation, use the zypper package manager supplied with Dr.Web Security Space. To do that, go to the directory /opt/drweb.com/bin and run the command:
For example:
If you want to uninstall Dr.Web Security Space, start the uninstallation script by running the command:
To reinstall a component, you can uninstall it first and then install again by starting custom or full installation. |