Modifying a Solaris JumpStart Example

Use the Trusted Solaris information that follows to modify the example in "Example of Setting Up and Installing Solaris Software With Custom JumpStart" in Solaris 8 Advanced Installation Guide.

In the Trusted Solaris environment, the Solaris JumpStart marketing and engineering example requires a user to assume the admin role.

In the Trusted Solaris operating environment:

• The site uses NIS+. The Ethernet addresses, IP addresses, and host names are in NIS+ tables.

• JumpStart information must use "None" for the naming service. Hosts installed by JumpStart are cliented after JumpStart finishes.

  Remote file systems are mounted after JumpStart finishes.

• All commands are done by a particular role at a particular label, usually ADMIN_LOW. To execute a command, the role must have the command at that label in its rights profile.

• All directories are created by the admin role at the label ADMIN_LOW, as in:

  $ cp -r /export/install/ts8_sparc/jumpstart_sample /jumpstart

  v

• To create a shared directory, in the admin role at label ADMIN_LOW follow the procedure in "Share the Network Install Directory" to create a vfstab entry, as in:

  ---

   share -F nfs -o ro,anon=0 /jumpstart

  ---

• To create a profile, the security administrator in the admin role at label ADMIN_LOW uses the Admin Editor action.

• To edit the rules file, the admin role at the label ADMIN_LOW uses the Admin Editor action.

• To execute the check script, the admin role at the label ADMIN_LOW runs the check(1M) script, as in:

  $ cd /jumpstart $ ./check

Set up the engineering systems for installation

On the install server, the admin role at the label ADMIN_LOW uses the add_install_client(1M) command:

$ cd /export/install
$ ./add_install_client -c server_1:/jumpstart host_eng1 sun4u
$ ./add_install_client -c server_1:/jumpstart host_eng2 sun4u
	.

Set up the marketing systems for installation

An administrator in the admin role at label ADMIN_LOW then uses the setup_install_server(1M) command that copies the boot software from the CD to the marketing server.

$ cd /cdrom/admin-cdrom_0/s0/Trusted_Solaris_8/Tools
$ ./setup_install_server -b /marketing/boot-dir sun4c

At label ADMIN_LOW, the admin role uses the add_install_client command on the marketing group's boot server.

$ cd /marketing/boot-dir
$ ./add_install_client -s server_1:/export/install \
-c server_1:/jumpstart host_mkt1 sun4c
$ ./add_install_client -s server_1:/export/install \
 -c server_1:/jumpstart host_mkt2 sun4c	...