Citrix* XenServer* 5.5.0 Installation Guide -
Intel® Server Board S3420GP
36
Intended target version: The intended target version is “5.5.0-build”.
Package Metadata
The “XS-PACKAGES” file describes the packages in a repository, one line per package. Fields are
separated by spaces. There are three types of packages:
tbz2 packages: Bzipped tarballs extracted onto the root file system.
Driver packages: Kernel modules loaded by the installer at runtime, and installed into the file
system.
Firmware packages: Available during the installation so they can be loaded by udev in addition to
being installed into the target file system.
Note: Firmware loading support is currently limited; this will be addressed in a future release.
There are four fields per package:
Package name.
Package size.
Package checksum (md5).
Package type.
The first three fields listed above are mandatory. The package type (identified above) dictates the
contents of the subsequent fields. If the type is “tbz2”, the subsequent fields are:
Required or optional.
Source filename.
Destination (usually “/”).
An example of this type, described above, is:
docs 37750 2ba1783d84d10c71f07469252c555427 tbz2 required docs.tar.bz2 /
If the type is “driver”, the subsequent fields are:
Source filename.
Destination. (${KERNEL_VERSION} is substituted with the Xen-kernel version)
An example of this type, described above, is:
firmware_example 77001 3452c04dfcc237cde11c63d43e97a303 driver \
firmware_example.ko \
/lib/modules/${KERNEL_VERSION}/extra/firmware_example.ko
Note: The back-slashes at the end of lines in the examples in this section denote continuation of
lines. Do not include them in a “XS-PACKAGES” file.
If the type is “firmware”, the subsequent field is:
Destination filename. (no path is necessary - it is automatically prefixed with “/lib/firmware/”)
An example of this type, described above, is:
firmware 12 6f5902ac237024bdd0c176cb93063dc4 firmware sample_firware.bin
To Next Page
Loading...
Need help?
General
