 | |||||||||||
| |||||||||||
 |
|||||||||||
| |
| ||||||||||||||||
Aptus supports most of the common Linux distributions that use the Linux 2.4 series kernel and glibc 2.2, 2.3 OSes. Please refer to the latest release notes of Aptus 2.0 which a copy of it should be in your Aptus 2.0 CD-ROM and it is also available from ShaoLin Microsystems Official website.
Aptus support stock kernels, that means which are the kernels that are pre-compiled and distributed by the above distributions originally or updates. If you which to use other customized kernel, please contact sales@shaolinmicro.com .
The following software must be installed before you can install ShaoLin Aptus. These packages normally comes with a standard Linux distribution, so you should install it first when you first setup your Linux box.
The network time protocol daemon ntpd, ntp-4.1.0 or above.
The NFS utilities nfs-utils, nfs-utils-0.3.1 or above.
The NIS client ypbind, ypbind-1.8-1 of above.
The NIS server ypserv, ypserv-1.3.12 of above.
The TFTP server tftpd if you want to use PXE.
The inetd or xinetd to use tftpd.
XFree86, you will need this to run X-Windows system XFree86, XFree86-4.1.0 of above.
Glibc 2.2 . The GNU libc libraries.
stat-2.x or above. A tool for finding out information about a specified file.
You can check it with the command rpm -q <package-name>" to see if it is installed. If not, they are always available from your original Linux installation CD's .
Since Aptus shares all the files including program files from the server with the client. You have to make sure the application binaries (program files) you've installed at the server are compatible with your client CPU. RPM packages have a file extension to indicate which CPU type it is compiled for and are described in the following way
i686, Intel Celeron, Pentium II/III/IV/Xeon, AMD Athlon, Duron, VIA C3-II
i586, Intel Pentium/MMX, Cyrix 5x86, IBM 6x86, AMD K6, Via C3 and Winchip
i486, Intel 80486
i386, All Intel 80386 compatible.
If your client are using different CPU type with the server, distribution installer might have installed some binaries that are not compatible with your client CPU. For example, you have a Pentium III server, and a Pentium or K6 client, it is likely your Linux distribution will have an optimized version of glibc package for your CPU, glibc-2.2.5.i686.rpm package which is not compatible with the client CPU (i586 this case). You can check by the following command rpm -q <package name> --qf "%{NAME}.%{VERSION}.%{ARCH}" to see if this is your case. Usually the rest of the packages are i386 compatible.
To fix this problem, you have to locate the corresponding package and use a binary compatible version. Usually you can find it in your Linux CD, you should able to find older CPU supported packages like i386 and i586. For the above example, the package glibc-2.2.5.i586.rpm will be suitable for both client and server. You have to use the command rpm -Uvh --force glibc-2.2.5.i586.rpm, to force installing the same package with a different architecture. For glibc problem, you will also have to remove the directory /lib/i686 at the server and run the ldconfig command to complete the process.
