User's Manual

Preparing the Directory Structure for Deployment in Embedded Linux 101

If you plan to run a scripted deployment from the DTK sample scripts, ensure

that the following files are correctly structured in the deployment directory. The

DTK sample scripts use this structure to set the default paths for deployment. If

you make changes to the directory structure, you must also make changes to the

sample scripts. The deployment directory structure consists of the following files:

• DTK utilities and files

• System-specific directories

• Operating system installation files directories

DTK Utilities and Files

All necessary DTK files are provided on the ISO image. The sample scripts

provided with the DTK are set up to use the default paths.

NOTE: If you choose to create a directory structure for the DTK components that is

different from the one provided in the initial installation, carefully review and edit

each sample script (where necessary) to reflect the different directory structure.

NOTE: The unzip utility is needed to create the Dell utility partition. This utility

should be copied into the /systems folder.

System-Specific Files

The directory /opt/dell/toolkit/systems/system name acts as a central repository

for all the system-specific deployment information. The /systems folder

acts a repository for the common files required for systems. For example, you

can store all profile configuration files for an optimally configured

PowerEdge™ 2850 in the directory /opt/dell/toolkit/systems/pe2850. These

files can then be accessed from this directory when deploying multiple

PowerEdge 2850 systems. For more information about obtaining Dell utility

partition files, see "How to Obtain Dell Utility Partition Files."

This directory can also be subdivided into multiple system-specific directories such

as: /opt/dell/toolkit/systems/pe2850 for Dell PowerEdge 2850 systems and

/opt/dell/toolkit/systems/pe1850 for Dell PowerEdge 1850 systems. See Figure 7-3.

NOTE: You should mount the network share on to the target system in the master

deployment file you created.

NOTE: If you choose to create a directory structure for the system-specific files that is

different from the one suggested in this guide, be sure to carefully review and edit each

sample script (where necessary) to reflect the different directory structure.