Alternatively, you can copy the new kernel and initrd to
/srv/SLEPOS/boot
with
new file names (for example
initrd-2.6.27.25.gz
and
linux-2.6.27.25
).
In such a case, you must create a new
scDistributionContainer
object (see
Section 10.3.5, “scDistributionContainer” (page 140) and add a new
scPosImage
object to it (see Section 4.6.1, “Deploying New Versions of System Images” (page 44)).
4.6 Copying the System Image Files
System images must be located in the
/srv/SLEPOS/image
directory on the Ad-
ministration Server. The boot image must be located in
/srv/SLEPOS/boot
. The
Branch Servers can then download the image files and deploy them on Point of Service
terminals. If the images have been built on the same machine, use the following
cp
command or your favorite file browser :
1
Use the following command to copy the system images to the
/srv/SLEPOS/
image
directory (type the command all on one line):
cp
/var/lib/SLEPOS/system/images/
image_name
/
image_name
.
architecture-version
/srv/SLEPOS/image/
image_name
.
architecture-version
2
Use the following command to copy the corresponding MD5 checksum files to
the
/srv/SLEPOS/image
directory (type the command all on one line):
cp
/var/lib/SLEPOS/system/images/
image_name
/
image_name
.
architecture-version
.md5
/srv/SLEPOS/image/
image_name
.
architecture-version
.md5
3
You can compress the images with the
gzip
compression utility. Run the fol-
lowing command on Administration Server:
gzip /srv/SLEPOS/image/image_name.
architecture-version
The compressed image is identified by the suffix
.gz
and handled accordingly,
no further actions are required. The POS scripts detect the
.gz
suffix and add a
“compressed” flag during
config.MAC
file generation (see also Section 7.7.1,
“The config.
MAC
File” (page 94)).
Setting Up the Administration Server
43