HP DL785 Sun Solaris 10 Deployment Guide for HP ProLiant Servers - Page 30

GRUB preparation, Overview of GRUB preparation

Get HP DL785 - ProLiant - G5 PDF manuals and user guides
UPC - 883585262809
View all HP DL785 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

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. 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. Deployment tasks 30

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
Deployment tasks 30
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.
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
.
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.