 |
» |
|
|
|
In this section, we will use Ignite-UX to customize an OS
install. Chapter 9 explains how this can be done with no user/administrator
interaction. Run Ignite-UX by executing this as root: /opt/ignite/bin/ignite When the target has rebooted (using either bootsys or manual network boot), and is ready for installation,
it will appear as an icon, labeled either as its original hostname
(if rebooted using bootsys), or by the hostname supplied by DHCP, or at Ignite-UX
screen. Select or click the icon of the system you wish to install. Select Actions -> Install Client -> New Install You should now see the Ignite-UX screen with five tabs across
the top. (If you see the System Hardware Inventory screen, simply
select OK to bypass it). In the Basic tab (the top tab at startup), select:
Configurations: -> HP-UX B.11.00 archive Ensure that the Root Disk, Root Swap and other fields are
correct for your installation. Any disks you select here
will be over-written! If you have a disk with existing
user information you don't want to modify, add it manually
after Ignite-UX has installed the OS. In the Software tab: Because there is only an archive at this point, the screen
is blank. We'll add a patch and application depot later. In the System tab, select:
Final System Parameters -> Set parameters now
Fill in the blanks with the correct data. Also fill in the appropriate data under Set Time Zone, Network Services... and, optionally, Set Root Password In the File System tab: Verify the correct disk usage. You can also add disks
at this point or modify the disk and file system parameters. A newfs
will be performed on all selected disks! In the Advanced tab: Nothing to specify here at this time. Later, we'll
add post-process scripts to execute. When finished entering data, select Go! Review the data in the configuration dialog box and select Go! again. To display target installation status, double-click
the target system icon on the Ignite-UX screen during execution.
Done!In less than 30 minutes, the target system should have the
new OS installed, a new kernel built, and the system rebooted and
ready for use. Status of the target system will be shown on its
icon, and in the status screen. When using the Ignite screen Ignite-UX determines the state of a target by reading the
files in the /var/opt/ignite/clients/LLA directory. Seeing an icon on the Ignite-UX screen does
not mean that the target actually exists, only that its config and
control files exist in the Ignite-UX directories. We can use this
behavior to our advantage to reinstall systems. This means that
if you are reinstalling a system that Ignite-UX has already installed,
you may need to either re-execute bootsys or boot the client from the Ignite-UX server. |
Printable version
