SystemImager® v4.0.2 Manual | ||
---|---|---|
<<< Previous | Installing SystemImager | Next >>> |
The official packages of SystemImager are distributed in the file release system on SourceForge.net at this link: https://sourceforge.net/project/platformdownload.php?group_id=259 ).
SystemImager depends on the System Configurator package that is also available on SourceForge: https://sourceforge.net/project/showfiles.php?group_id=24006 ).
A quick way to download all the required packages is to run the sis-install script (replacing i386 with the architecture of your clients):
$ mkdir systemimager $ cd systemimager $ wget http://download.systemimager.org/pub/sis-install/install $ chmod u+x install $ ./install -v --download-only --tag stable --directory . \ > systemconfigurator \ > systemimager-client systemimager-common \ > systemimager-i386boot-standard systemimager-i386initrd_template \ > systemimager-server \ > systemimager-bittorrent systemimager-flamethrower |
Use ./install --help for more informations.
Install all the base packages in the image server. In RPM-based distributions run:
# rpm -ivh systemconfigurator-*.rpm \ > systemimager-common-*.rpm systemimager-server-*.rpm \ > systemimager-*initrd_template-*.rpm systemimager-*boot-standard-*.rpm |
# dpkg -i systemconfigurator-*.deb \ > systemimager-common-*.deb systemimager-server-*.deb \ > systemimager-initrd_template-*.deb systemimager-boot-*-standard-*.deb \ |
If you want to use the BitTorrent transport install also the systemimager-bittorrent package. RPM package:
# rpm -i systemimager-bittorrent-*.rpm |
# dpkg -i systemimager-bittorrent-*.deb |
If you want to use the Multicast transport install also the systemimager-flamethrower package. RPM package:
# rpm -i systemimager-flamethrower-*.rpm |
# dpkg -i systemimager-flamethrower-*.deb |
If your clients have multiple architectures download also the appropriate systemimager-ARCHboot-standard and systemimager-ARCHinitrd_template in your image server.
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.9.6 release should have these packages:
systemimager-boot-i386-standard_3.9.6-1_all.deb,
systemimager-boot-x86_64-standard_3.9.6-1_all.deb,
systemimager-boot-ppc64-ps3-standard_3.9.6-1_all.deb,
...
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 multiple boot flavors can be installed simultaneously.
To create a custom flavor perfectly compatible with the distribution you can exploit the UYOK (Use Your Own Kernel) feature. Standard flavors use a general purpose kernel that supports a lot of hardware components, but obviously they can't be able to support all the possible devices that could be present in a totally generic client (see also hardware with proprietary drivers). For this reason starting from 3.6.x the UYOK (UseYourOwnKernel) feature has been introduced. This feature allows you to use the same kernel that runs in your golden client to perform the installation in other clients. In this way it's possible to theoretically support all the hardware/components you could have. Simply if the kernel of your distribution is working well with your clients, it works well too to install them. For more informations see http://wiki.systemimager.org/index.php/UYOK.
<<< Previous | Home | Next >>> |
Selecting A Machine To Use As An Image Server | Up | Selecting A Machine To Use As A Golden Client |