User's Manual

80 Choosing an Embedded Linux-Based Deployment Method
This deployment method is the easiest to assemble, but is the least flexible.
Any change to the system configuration, for example, requires the creation of
a new bootable CD. This method does not provide a writable media making it
necessary to use predefined and tested configuration files.
Creating a Bootable CD
Bootable CDs can be created using any commonly available CD burning
software in a two-part process that requires a self-bootable ISO image with
drivers that load from system files. When you create a bootable CD, this
image is supplied to the CD burning software along with the complete
deployment directory structure, which includes all necessary supporting files
to perform the deployment. The CD burning software creates an image of the
self-bootable ISO image and the deployment files on the CD.
NOTE: See ""Running Deployment Scripts and RPMs Using DTK and Embedded
Linux" on page 125" for more information about creating an embedded Linux-
bootable CD.
Using DTK Utilities and Scripts From a Bootable CD
The bootable CD can be configured to start and execute the master
deployment file during the booting process. The master deployment file
performs all necessary pre-operating system configuration tasks and then
installs the operating system from the files in the deployment directory
structure on the CD.
NOTE: You must write the master deployment file. This file is not provided with the
sample scripts.
NOTE: You must create a RAMDISK for temporary data storage when using a
bootable CD for a local deployment.
Using DTK RPMs from a Bootable CD
Besides the utilities and scripts, the CD contains DTK RPMs that provides all
the DTK tools such as syscfg, raidcfg, and racadm. The RPMs can be used
individually or in groups as per the requirements.
NOTE: DTK RPMs is supported on both 32-bit and 64-bit architectures.