User's Manual

Choosing an Embedded Linux-Based Deployment Method 79
system—the space on a network share can be very large, and a single set of
utilities and scripts can be accessed by many systems, making the deployment
process easy to manage.
After a network drive is mapped from a target system to a network share, all of
the utilities and scripts are available to use. The master deployment script on
the network share can be called from the bootable CD to perform a task or
multiple tasks on the target server. For example, pre-operating system
configuration tasks can be deployed from the network and operating system
files can be installed.
Creating a Customized Bootable CD with Network Stack
See "Running Deployment Scripts and RPMs Using DTK and Embedded
Linux" for details on how to create a customized version of a single embedded
Linux bootable CD that works across all Dell systems and provides an
underlying network stack.
Using a Third-Party Deployment Solution Framework
You can use DTK with any existing third-party deployment solution
framework that provides a
PXE booting infrastructure that can be used as the
transport mechanism for DTK utilities. Because each third-party deployment
framework is unique, however, these solutions fall outside the scope of this
document. If you plan to utilize a third-party deployment solution
framework, keep in mind that DTK is an embedded Linux-based set of tools
and scripts, so the deployment solution framework must also support
embedded Linux as a pre-operating system environment.
CD-Based Local Deployment for Embedded Linux
The general CD-based deployment process includes the following steps:
1
Copy the DTK ISO image into a share.
2 Modify the appropriate section in the isolinux / isolinux.cfg file.
3 Reburn the contents into a CD (which will be the master CD).
4 Boot the target server from the master CD.
The DTK startup phase mounts the CD.
The DTK startup phase runs the script (name specified in the
isolinux.cfg
file) from the CD.