SRR Module : The srripc Linux Kernel Module, Version 1.4.21
	Chapter 2. Installation

Chapter 2. Installation

Table of Contents

2.1. Unpacking the Archive
2.2. Testing the SRR Module
2.3. Installing the SRR Module
2.4. Enabling Auto-Loading for the SRR Module
2.5. Example Code

The library installs as a dynamically loadable kernel module. It has been allocated an official minor number from the kernel's miscellaneous minor-number space.

2.1. Unpacking the Archive

The SRR Module is shipped as a gzipped tar file.

If you download the archive using a Windows based browser you may find that the browser saves the archive as a .gz file instead of a .tgz file. If this happens, simply modify the file extension to be .tgz before proceeding.

To unpack the archive in preparation for installation, follow this procedure:

Log in as root, or su to root.
Download or move the srr-x.x.x.tgz file to a temporary directory and then cd to that directory.
Issue the tar command:
```
# tar xzvf srr-x.x.x.tgz
```
This will create the directory srr-x.x.x/ and its sub-directories.
Change to the srr-x.x.x/ directory:
```
# cd srr-x.x.x/
```
Issue the make command:
```
# make
```

Version 2.6 users: Compiling using kernel headers rather than original kernel source will not work for Linux version 2.6 as it does for Linux version 2.4. You need to have a link from the /lib/modules/... directory tree to the include directory. For most Linux distributions there is an installation package that installs the kernel source and sets up this link. If you are using an unmodified kernel, you will have to apply this package. If you are using a modified kernel, the kernel build should have created the link. You can check this by looking for the link:

/lib/modules/release_name/build

which was created from the expansion:

/lib/modules/$(uname -r)/build

on your Linux installation. If this link is not there, or it has a slightly different name, then the SRR Module build will fall back to the /usr/include headers, which will almost certainly fail. If so, you will probably get warnings from errors in headers from the /usr/include tree during installation.

If you have the kernel source installed, but do not have the /lib/modules/release_name/build directory, you can create it by creating the link explicitly in the proper directory, pointing to the root of the kernel source tree, such as:

ln -s	/usr/src/my_kernel_source /lib/modules/$(uname -r)/build

where /usr/src/my_kernel_source is the actual location of the kernel source.

The compile might still fail if you have never built this kernel source tree. You do not actually have to build the whole kernel tree, though, just enough to create config.h and possibly some links. You can do this by running make menuconfig in the kernel source directory, then just save and exit. Then run make modules and let it build a couple of modules.

That done, you should be able to build the SRR Module. It should build with no warnings.


1.3. OS-Specific Behavior		2.2. Testing the SRR Module