HP Hitachi Dynamic Link Manager Software - Manual (Page 244)

3. Creating an HDLM Environment
220
initrd-2.6.16.46-0.14-default.hdlm was created.
KAPL12330-I The utility for supporting the boot disk
completed.
24. When you create a new initial RAM disk image file rather than overwriting the
existing one, delete the existing initial RAM disk image file that is no longer
required.
Execute the following command:
• Execution example of the command when GRUB as the boot loader is used
# rm /boot/initrd-hdlm-2.6.9-11.EL.gz
• Execution example of the command when IPF (with ELILO as the boot
loader) is used
# rm /boot/efi/efi/redhat/initrd-hdlm-2.6.9-11.EL.gz
25. Edit the
/etc/fstab
file.
Change the
/boot
mount point that you changed in step 4 from the SCSI device
to the HDLM device. Comment out the existing SCSI device specification by
placing a hash mark (
#
) at the beginning of each line, and then add the HDLM
device specification as shown below, based on the correspondence between the
HDLM device and the SCSI device as checked in step 21.
:
:
#/dev/sda1 /boot ext3 defaults 1 2
/dev/sddlmaa1 /boot ext3 defaults 1 2
:
:
This example assumes that IA32 uses
GRUB
as the boot loader. When you use IPF
that uses
ELILO
as the boot loader, the mount point is displayed as
/boot/efi
instead of
/boot
in the line where
/boot
is coded, and the file system type is
displayed as
vfat
instead of
ext3
.
26. Edit the boot loader configuration file so that the OS will start with HDLM
specified.
Edit the boot loader configuration file as shown in Figure 3-20: Example of
Editing /etc/grub.conf file, Figure 3-21: Example of Editing /boot/grub/menu.lst
file (When using a kernel that supports Xen), and Figure 3-22: Example of
Editing /etc/elilo.conf file.
If you are using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterprise