########################################################################

has_ps2 { _hp_keyboard = {

"Not_Applicable", "PS2_DIN_US_English", "PS2_DIN_US_English_Euro"

}

init _hp_keyboard = "PS2_DIN_US_English"

}

has_usb { _hp_keyboard = {

"Not_Applicable",

"USB_PS2_DIN_US_English", "USB_PS2_DIN_US_English_Euro"

}

init _hp_keyboard = "USB_PS2_DIN_US_English"

}

Instances that may require modifying os_arch_post_l

There are circumstances in which you may want to modify os_arch_post_l. For example, the following excerpt is from the os_arch_post_l script:

#

#Networking files:

#/etc/hosts

#/etc/resolv.conf

#/etc/rc.config.d/namesvrs

#By default, these files will be constructed from the information

#in the config file. The starting point for the hosts file is the

#/usr/newconfig version, which just has a loopback entry. The other

files

#are built from scratch. To get the archive versions of these files,

#uncomment only the save_file lines here and comment out the rm line.

#Using save_file will restore the file as-is from the archive. Using

#merge_file will allow Ignite-UX to make changes to the file based

#on what the config file or changes made in the UI.

#

#save_file /etc/hosts #merge_file /etc/hosts rm -f /etc/resolv.conf #save_file /etc/resolv.conf #merge_file /etc/resolv.conf

#save_file /etc/rc.config.d/namesvrs #merge_file /etc/rc.config.d/namesvrs:

By default, during an installation 88 from an archive, the final versions of these files are taken from /usr/newconfig. If you have a complex configuration that needs to be preserved from the archive version of the file, you must uncomment the corresponding merge_file entry.

For example, if your /etc/hosts file contains extra entries that you need to preserve, you would uncomment the merge_file /etc/hosts line in your os_arch_post_l script. In the case of /etc/hosts, it may not be a good idea to use save_file as it means that any changes Ignite- UX made to /etc/hosts would be overwritten by the version saved from the archive.

88This does not apply to recovery situations. A merge_file is executed for the files in the os_post_arch_l script. You can find out what files maybe merged or saved automatically in a recovery situation by searching os_arch_post_l for "RECOVERY_MODE".

201