Installing a Custom Operating System with HP Insight Control for Linux

11
If the extra_files script exists, Insight Control for Linux runs it during the Configure System to Boot
from Network operation when you install an OS. Insight Control for Linux captures the output of the
extra_files script and copies those files to the ISO it creates.
Insight Control for Linux passes the GUID.vars file name as an argument when Insight Control for
Linux starts the extra_files script. The extra_files script must then source in the GUID.vars file
to access the variables contained in the file. For an example of a bash script that sources the
GUID.vars file, see
Sourcing in the GUID.vars file.
The GUID.vars file contains a variable, boot_dir, that points to the directory containing the files
needed for booting; this variable is shown in the example of the comma-separated list. Use this
variable to construct a path to the additional files that need to be copied to the ISO.
The full path name and location of this script must be:
/opt/repository/instconfig/custom/MyOS/extra_files
Where MyOS is the OS name you specified in the Name field when you registered your Custom OS.
Make sure that the root user has execute permission for the extra_files script.
Alternative ISO creation
Insight Control for Linux uses the /opt/hptc/bin/create_iso script to create an ISO containing
the operating system’s kernel and a RAM disk that will be booted using virtual media. If your custom
OS requires some special way of creating the ISO, such as an alternate ISO directory structure, you
can create and call your own create_iso script. The name and location of this script must be:
/opt/repository/instconfig/custom/MyOS/create_iso
Where MyOS is the name of the operating system you specified in the Name field when you
registered your custom OS in the Insight Control for Linux repository (see
Registering your custom
operating system).
HP recommends that you copy the /opt/hptc/bin/create_iso script and customize it.
Make sure that the root user has execute permission for the create_iso script.
File Map
The following illustration provides a hierarchical view of the files mentioned in the white paper. File
names in blue are required only for interactive installations. File names in green apply only to
installations using virtual media.