(disk[_hp_root_disk].size<400000Mb)

{

_hp_disk_layout="N4000 with 36Gb disk"

}

else

{

_hp_disk_layout="N4000 with 72Gb disk"

}

}

}

}

The difference between the two sets of configuration is that the init keyword is missing from the second set of configuration statements when _hp_disk_layout is set to be a specific value. The instl_adm(4) manpage states:

init variable=value

the init keyword

means that

the

Preceding the assignment with

variable is to be initialized

to the given value, but the

user

interface is allowed to alter

the value later.

 

 

variable=value

When the init keyword is not used, then the variable cannot be changed by the user interface. This type of assignment is not recommended for "visible" variables.

Therefore, the init keyword must precede the value that _hp_disk_layout is set to; otherwise the Ignite-UX GUI cannot change it. When you modify anything using the Ignite-UX GUI, it wants to add a new value to the list that _hp_disk_layout can have and set it to the value of _hp_disk_layout. Unless init is used to give _hp_disk_layout its initial value, the Ignite- UX GUI cannot change it and all modifications to the disk layout are lost.

If you have an Ignite-UX server and a client that has been added or installed recently, you can test this as follows:

1.Enter:

cd /var/opt/ignite/clients itool –m pull –d <client>

2.Change the type of disk layout by selecting the File system tab and choosing the correct layout from the list.

3.Quit the Ignite-UX GUI. You can choose any option on the exit screen; none of the options reboots or halts the system.

4.Edit /var/opt/ignite/clients/<MAC>/config and remove init from the front of the _hp_disk_layout variable.

5.Save the file.

6.Rerun the Ignite-UX GUI using the itool command in Step 1. If you change the file system layout, it reverts to the original value.

89