1
Use the following command to copy the initrd file to the
/srv/SLEPOS/boot
directory as
initrd.gz
(type the command all on one line):
cp
/var/lib/SLEPOS/system/images/
image_name
/initrd-netboot-
image_name
.
architecture-version
.gz
/srv/SLEPOS/boot/initrd.gz
2
Use the following command to copy the kernel file to the
/srv/SLEPOS/boot
directory as
linux
(type the command all on one line):
cp
/var/lib/SLEPOS/system/images/
image_name
/initrd-netboot-
image_name
.
architecture-version
.kernel.
kernel_version
/srv/SLEPOS/boot/linux
If the images have been built on a dedicated Image Building Server, use the
scp
com-
mand or the remote copy option of your file browser:
1
Use the following command to copy the initrd file to the
/srv/SLEPOS/boot
directory as
initrd.gz
(type the command all on one line):
scp
/var/lib/SLEPOS/system/images/
image_name
/initrd-netboot-
image_name
.
architecture-version
.gz
adminserver_address
:/srv/SLEPOS/boot/initrd.gz
2
Use the following command to copy the kernel file to the
/srv/SLEPOS/boot
directory as
linux
(type the command all on one line):
scp
/var/lib/SLEPOS/system/images/
image_name
/initrd-netboot-
image_name
.
architecture-version
.kernel.
kernel_version
adminserver_address
:/srv/SLEPOS/boot/linux
4.5.1 Deploying Boot Images with a New
Kernel Version
If you build images with a new kernel version, you can preserve old file names and
overwrite existing images. In such a case, there is no need to update objects in LDAP
database.
42
SUSE Linux Enterprise Point of Service Guide