User's Manual

122 Preparing the Script Files for Deployment Using Embedded Linux
lininst.sh
The lininst.sh sample script is used to perform an unattended installation of
a supported Red Hat Enterprise Linux Server operating system. The variables
and paths must be specified before the operating system can be installed.
NOTICE: It is strongly recommended that you consult your Red Hat Enterprise
Linux Server operating system documentation and unattended deployment
documentation to develop a thorough understanding of the unattended installation
process before attempting to perform a full scripted deployment.
Utilities Used
grub — Used in conjunction with the kernel image and initial ramdisk files,
along with the unattended answer file to install the operating system.
Variables Used
• DT_OS_DISK — Sets the disk on which to deploy the Red Hat
Enterprise Linux Server operating system.
• DT_OS_SRC — Sets the location from where to copy the kernel image
and
initial ramdisk files.
External Dependencies
The DT_PLATFORM variable is set during deployment by tkenvset.sh using
platform discovery.
The lininst.sh script uses the
unattended answer file in conjunction with the
grub utility and kernel image and initial ramdisk files to install the operating
system files. See "ks.cfg (for Red Hat Enterprise Linux Server Versions 3 and 4)
and ks-rhel5.cfg (for Red Hat Enterprise Linux Server Version 5)" for more
information about preparing the
unattended answer file.
ks.cfg (for Red Hat Enterprise Linux Server Versions 3 and 4) and
ks-rhel5.cfg (for Red Hat Enterprise Linux Server Version 5)
Depending on the version of the Red Hat Enterprise Linux Server operating
system, the ks.cfg or ks-rhel5.cfg files are the default names of the answer files that
you use to automate an unattended Red Hat Enterprise Linux Server installation.
A sample copy of the ks.cfg/ ks-rhel5.cfg files are provided as part of the DTK
download in the /opt/dell/toolkit/template/configs directory. The ks.cfg/ks-
rhel5.cfg files contain the headings and parameters that instruct the installation
utility to perform various configuration tasks. Before a full deployment can be run,
you must edit all appropriate headings and parameters, as necessary.