user manual

Deployment tasks 28
Preparing the RDP deployment server
To configure the RDP deployment server:
1. Copy the example script examples/rdp/sol.sh from the resource kit to
...\lib\bin32\linux\ on the deployment server. This script is called by the Create Boot
Environment task script in the Solaris RDP job.
2. Create a new directory under ...\lib\osdist on the deployment server to store the Solaris
multiboot program and miniroot, for example ...\lib\osdist\sol10_1106. Copy the Solaris
multiboot program and the modified miniroot into the new directory. The multiboot program and
miniroot must be named multiboot and x86.miniroot, respectively.
3. Import the example job included in the resource kit (examples/rdp/deploy-sol.bin) to the
deployment server console.
4. Modify the script in the Create Boot Environment task in the newly imported example job to match
the target environment. The example script is well-commented and is self-explanatory.
GRUB preparation
This section describes GRUB menu configuration file preparation for use in deploying Solaris. For more
information about GRUB, see GRUB and the Solaris 10 1/06: The New Bootloader for x86 Platforms and
GNU GRUB Manual 0.97 at http://www.gnu.org/software/grub/manual/html_node/index.html
.
Overview of GRUB preparation
When GRUB loads, it scans for a configuration file that usually contains the definition of the menu that
GRUB should display. Each menu item is associated with a series of GRUB commands that GRUB
executes when that menu option is selected. For Solaris, the GRUB configuration file is usually named
menu.lst.
The easiest way to create a custom configuration file is to use the menu.lst from the Solaris media as a
template. This list is on the DVD or the first CD, or under the installation media root directory on the install
server, as .../boot/grub/menu.lst. Each title line defines a menu option, and the commands that
follow the title line are the commands that GRUB executes when that menu option is selected.
NOTE: For commands in menu.lst, each command list is implicitly terminated with a boot
command. When entering commands manually at the GRUB command line, the boot command
must be explicitly given.
To boot a Solaris miniroot, the Solaris multiboot program and miniroot module must be loaded. To boot
into a network deployment, the proper boot options for installation media location and JumpStart
configuration must be provided.
The following sections describe the various boot options and provide examples.