Log in to the N1 System Manager.
Copy the custom OS update to the N1 System Manager.
N1-ok> create update update updatetype other file file ostype ostype installscriptfile installscriptfile [adminfile adminfile] [responsefile responsefile]
Even though the tab completion allows this argument anywhere in the create update command, the command will fail if updatetype other is not the first argument.
Use the tab completion help to find out the valid ostype values.
This example shows an executable Bourne shell (/bin/sh) patch installation script.
#!/bin/sh mkdir /tmp/layer cd /tmp/layer echo "untar the source:" tar -xvf /tmp/mypatches.tar echo "let's install mypatches:" patchadd -M /tmp/layer 117448-01 117466-01 cd /tmp rm -rf /tmp/layer exit $?
The following sample command shows how to copy the patch installation script to N1 System Manager with the OS update files. This example assumes that you have copied the script to the management server's /tmp directory with the name install.sh.
N1-ok> create update mypatches updatetype other file /tmp/mypatches.tar ostype solaris10x86 installscriptfile /tmp/install.sh
In this example, /tmp/mypatches.tar contains the Solaris patches 117448–01 and 117466–01 in the datastream format.
The script and the source files for the OS update are copied to the target server when the load server server-name update command is issued. The script file is executed by using the Bourne shell with the full path to the package file as the sole argument.