Version 1 by Nathan McCoy
on Jul 08, 2016 17:05.

compared with
Version 2 by Nathan McCoy
on Mar 31, 2017 11:16.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (9)

View Page History


!test-connection.png!


h2. 2. Installing kernel sources



!yum-kernel.png!


h2. 3. Verifying that the source matches your running kernel

h3. Option 1: Building online

(Direct Internet connection to R1Soft build server).
_(Direct Internet connection to R1Soft build server)_

To attempt to build the kernel module, run the following command (this may take several minutes):
{code}


!getmodule.png!

h3. Option 2: Building offline

_(Without direct Internet connection to R1Soft build server)._

If there is no direct Internet connection between your Server Backup and R1Soft build server, it is still possible to compile the kernel module. In this case, this will be tree-step process. First, you will have to create tarball file with the kernel headers. When you should copy this tarball file from the server to some other computer which has Internet connection to R1Soft build server. From this computer you should upload the tarball to the R1Soft build server and wait for the compilation to finish. When it is finished, you should download binary module and copy it back to Server Backup. Start with executing the following command:
If there is no direct Internet connection between your Server Backup and R1Soft build server, it is still possible to compile the kernel module. In this case, this will be a three-step process. First, you will have to create a tarball file with the kernel headers. Then, you should copy this tarball file from the server to some other computer that has an Internet connection to an R1Soft build server. From this computer, you should upload the tarball to the R1Soft build server and wait for the compilation to finish. When it is finished, you should download the binary module and copy it back to Server Backup. Start by xecuting the following command:

{code}serverbackup-setup --no-binary --kernel-dir /usr/src/kernels/YOUR_KERNEL_TREE


!no-binary.png!


When the tarball ( {{.tar.gz}} ) file has been written to disk, perform the following steps: