User's Manual

Running Deployment Scripts and RPMs Using DTK and Embedded Linux 129
• Drivers for all your hardware installed in your embedded Linux (from the
Dell Support website at
support.dell.com )
• Serial port configuration utilities (
setserial and stty ) for racadm
• Installed and working instrumentation drivers (from /mnt/cdrom/tools )
• Point-to-Point Protocol (PPP) tools
• Basic libraries and utilities for Linux to execute customized scripts
• DTK tools and utilities extracted from the embedded Linux CD
(
/mnt/cdrom/tools/dell.tar.gz)
• Necessary entries in the ld.so.config file so that the libraries get loaded
Integrate all the above mentioned libraries, Dell toolkit libraries, tools, and
utilities into your embedded Linux environment and proceed with deployment.
NOTE: Ensure that the raidcfg executable in the /bin directory is a symbolic link to
the raidcfg in the Dell-provided /lib folder.
NOTE: Refer to start-stage3.sh, start-hapi.sh, or start-raid.sh on /mnt/cdrom/tools
to see how Dell-provided utilities and drivers are loaded.
NOTE: The /opt/dell/srvadmin/shared and /opt/dell/srvadmin/hapi directories
should have Read-Write permissions. Refer to start-stage3.sh and start-hapi.sh
for details.
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.