????

Your IP : 3.144.117.52


Current Path : /proc/self/root/usr/lib/Acronis/BackupAndRecovery/
Upload File :
Current File : //proc/self/root/usr/lib/Acronis/BackupAndRecovery/HOWTO.INSTALL

TABLE OF CONTENTS

Introduction

I.   Building and installing the kernel module

II. FAQ:

    Q: How do I run the .i686 or .x86_64 installation file?

    Q: Is the .i686  installation file  compatible  with  my
x86_64 architecture?

    Q: Can I install the product on an IA64 system?

    Q: The setup program  cannot find kernel source files in
the /lib/modules/<MY_KERNEL>/build or the
/lib/modules/<MY_KERNEL>/source directory. What should I do?

INTRODUCTION

In  some  cases,  the  setup  program  cannot  compile  the 
necessary  kernel  modules or prepare the required execution
environment  for  the  product.  Normally, the setup program
informs you about this problem and  refers you to this file.

Section I  of this file describes  how to  build and install
the kernel module.  You may need to read that section if you
have a custom kernel or a nonstandard location of the kernel
source files.

I. BUILDING AND INSTALLING THE KERNEL MODULE

The  product  can  be  installed  in  the  following  Linux
distributions   with   kernel   from   2.6.9  to  5.1 and
glibc 2.3.4 or later:

    (a) Red Hat Enterprise Linux 4.x, 5.x, 6.x, 7.0, 7.1,
        7.2, 7.3, 7.4, 7.5, 7.6, 8.0

    (b) Ubuntu 9.10, 10.04, 10.10, 11.04, 11.10, 12.04,
        12.10, 13.04, 13.10, 14.04, 14.10, 15.04, 15.10, 16.04,
        16.10, 17.04, 17.10, 18.04, 18.10

    (c) Fedora 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21,
        22, 23, 24, 25, 26, 27, 28, 29, 30

    (d) SUSE Linux Enterprise Server 10 and 11
        SUSE Linux Enterprise Server 12 – supported on file
        systems, except for Btrfs

    (e) Debian 4, 5, 6, 7.0, 7.2, 7.4, 7.5, 7.6, 7.7, 8.0,
        8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 9.0, 9.1,
        9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.8

    (f) CentOS 5.x, 6.x, 7, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6

    (g) Oracle Linux 5.x, 6.x, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6
       --  both Unbreakable Enterprise Kernel and Red Hat
       Compatible Kernel

    (h) CloudLinux 5.x, 6.x, 7, 7.1, 7.2, 7.3, 7.4, 7.5

    (i) ClearOS 5.x, 6.x, 7, 7.1, 7.4

    (j) ALT Linux 7.0

In any of these  distributions,  the setup program  normally
automatically compiles  the kernel module  that is necessary
for the product to work.

If the setup program  cannot compile the kernel module,  you
will need to do this manually, as follows.

You need to install the kernel source files, the appropriate
configuration file,  and all packages that are  required for
building the kernel. These packages  include  "gcc", "make",
and   "kernel-devel".    You  will  be  prompted  about  the
necessary packages when installing the  kernel source files.

Normally,  you can  build and install the  "snapapi"  kernel
module by running the "dkms" commands as follows:

    # dkms build -m <MODULE_NAME> -v <MODULE_VERSION> \
     --config <CONFIG_FILE> --arch <KERNEL_ARCH> \
     --kernelsourcedir <PATH_TO_KERNEL_SOURCES>

    # dkms install -m <MODULE_NAME> -v <MODULE_VERSION> \
     --config <CONFIG_FILE> --arch <KERNEL_ARCH> \
     --kernelsourcedir <PATH_TO_KERNEL_SOURCES>

In these commands:

    <MODULE_NAME> must be one of the following:

        (a) For 2.4.x kernels: snapapi

        (b) For 2.6.x and 3.x kernels: snapapi26

    <MODULE_VERSION> is the version of the "snapapi" module.
You can determine it by running the following command:

        # ls /usr/src | grep snapapi

        For  example,  if  the  name  of  the  directory  is
snapapi26-0.7.64, the  value  of <MODULE_VERSION> is: 0.7.64

    <CONFIG_FILE> is  the name of your  kernel configuration
file.  This file is  usually located in the /boot directory.
Specify the full file name, for example:
/boot/config-2.6.31-14-generic

    <KERNEL_ARCH> is  the type of  kernel architecture,  for
example: i686. You can detect the value for <KERNEL_ARCH> by
running the following commands:

        (a) For  RPM-based  distributions,  such as  Red Hat
Enterprise Linux, CentOS, or Fedora:

            # rpm -q --queryformat "%{ARCH}\n" kernel

        (b) For  distributions  not  based on  RPM,  such as
Ubuntu:

            # uname -m

For details about using the dkms utility,  refer to the dkms
man page.

After  successfully  building  and  installing   the  kernel
module, you can run the product to  check its functionality.
The appropriate kernel modules will be loaded automatically.

II. FAQ

Q: How do I run the .i686 or .x86_64 installation file?

   A: This  is  a  standard   binary  file.   To  start  the
installation, run the following commands:

          # chmod +x <FILE_NAME>

          # ./<FILE_NAME>

      Here, <FILE_NAME> is the name of your .i686 or .x86_64
installation file.

      The setup program uses the  RPM Package Manager (RPM).
Before  installing  the  product  on a  system that does not
use RPM, such as an Ubuntu system,  you need to install RPM;
for example,  by running  the  following command as the root
user:

          #apt-get install -y rpm

Q: Is the .i686 installation file compatible with my  x86_64
architecture?

   A: No,  you  must download and install the  corresponding
.x86_64 installation file instead of the  .i686 installation
file. The installation procedure is the same.

Q: Can I install the product on an IA64 system?

   A: No, this architecture is not supported by the product.

Q: The setup program cannot find  kernel source files in the
/lib/modules/<MY_KERNEL>/build or in the
/lib/modules/<MY_KERNEL>/source directory. What should I do?

   A: This usually means that you need to install the kernel
source files corresponding to your kernel version.

      The following commands install the kernel source files
in Debian and Ubuntu:

       $ sudo apt-get update
       $ sudo apt-get install linux-headers-`uname -r`
       $ sudo apt-get install linux-image-`uname -r`
      
      The following command installs the kernel source files
in Red Hat Enterprise Linux and Fedora:

       # yum install kernel-devel-`uname -r`