To create a SystemImager image server, you must install a systemimager-boot package(s)and then a systemimager-server package that supports your clients.
The boot packages support multiple configurations. Because different client configurations require different drivers, kernel versions, etc., SystemImager allows you to install different boot packages, which are known as "boot flavors."
Each SystemImager release provides the "standard" flavors for each supported architecture. For example, the 3.0.0 release should have the packages systemimager-boot-i386-standard_3.0.0-1_all.deb, systemimager-boot-ia64-standard_3.0.0-1_all.deb, systemimager-i386boot-standard.noarch.rpm, and systemimager-ia64boot-standard.noarch.rpm
SystemImager and its standard boot flavors support most common hardware configurations. The .config files list the options for this kernel.
You can use other flavors at any time to support alternate client configurations, and mulitple boot flavors can be installed simultaneously. However, boot packages are strongly coupled to the version of SystemImager for which they were created. The SystemImager boot package versions strings should match the version string of the installed version of SystemImager.
To install an image server for Debian GNU/Linux 3.0 (woody) and later, run:
# apt-get update
# apt-get install systemimager-server
![]() | For Debian 2.2 (potato), you must add the following line to the /etc/apt/sources.list file: deb http://systemimager.org/debian / |
For RPM based distributions:
Download and install the systemimager-server RPM and required dependencies from http://systemimager.org/download/ .
Install each package with the rpm command.
# rpm -Uvh *.rpm
For other distributions: If your distribution does not support RPMs or .debs, you must use build and install from the source tarball; binary tarball installations are no longer supported. Instructions for building SystemImager can be found in the README file within the source tarball.