Setting Up Custom JumpStart Installation

In the Trusted Solaris environment, Custom JumpStart procedures are handled by administrative roles. For an explanation of Custom JumpStart, see "Preparing Custom JumpStart Installations" in Solaris 8 Advanced Installation Guide. Trusted Solaris software modifies Custom JumpStart procedures as it does other installations, with device allocation and task allocation by role. Note that the Trusted Solaris environment does not support mounting remote file systems during installation.

Factory-installed JumpStart may not be supported by Trusted Solaris software.

Create a JumpStart Diskette

This procedure is done by the admin role at label ADMIN_LOW.

1. In the admin role at label ADMIN_LOW, allocate the floppy drive.

   See "Allocate the Appropriate Device" if you are unsure of the steps.

2. Format the JumpStart diskette by running the fdformat command.

3. Create a file system on the diskette by running the newfs command.

4. Create a a mount point on the diskette by running the mkdir command.

5. Run the mount command.

   ---

   Example 7-2 Mount a UFS Filesystem on a Diskette

   
   

   To create a UFS file system on a diskette to be used for Custom JumpStart, as admin at ADMIN_LOW:

   $ mkdir /ts8_jumpstart $ mount -F ufs /dev/diskette /ts8_jumpstart

   ---

6. Run the cp command to copy the JumpStart sample directory to the diskette.

7. Share the directory.

   For details of the procedure, see "(Optional) Share File Systems".

8. Use the -c option to the add_install_client command to add JumpStart details to the install server's local bootparams database.

9. When you are finished with the JumpStart diskette, deallocate the drive and remove the diskette.

   See "Deallocate the Device" if you are unsure of the steps.

Edit a JumpStart Profile

1. When following the procedures in "Creating a Profile" in Solaris 8 Advanced Installation Guide, assume the admin role at label ADMIN_LOW, and use the Admin Editor action to edit a JumpStart profile.

   For how to use the Admin Editor, see "To Create or Open a File from the Trusted Editor".

   The upgrade keyword is not fully supported in the Trusted Solaris 8 4/01 installation program. If you want to upgrade Trusted Solaris 8 systems, this keyword should work.

Use pfinstall to Test a Profile

Use this procedure to modify the procedures in "Testing a Profile" in Solaris 8 Advanced Installation Guide and "pfinstall" in Solaris 8 Advanced Installation Guide.

In the Trusted Solaris environment, testing profiles is handled by the admin role, and modifying rights profiles is handled by the secadmin role.

1. On an installed and configured Trusted Solaris system, log in as a user who can assume the admin role.

2. As admin at label ADMIN_LOW, launch a terminal and see that the pfinstall(1M) command is available in the role's profile shell.

   $ profiles -l | grep pfinstall

   The name profile shell refers to a shell that recognizes rights profiles. It does not refer to the machine profiles being tested here.

3. If the command is not in the profile, the secadmin role must add it to the admin role's rights, and then the admin role launches a new terminal in which to run the command.

   See "Modifying a Role's Rights" for how to add the pfinstall command to the admin role's rights profile.

Edit a Rules File

1. When following the procedures in "Creating the rules File" in Solaris 8 Advanced Installation Guide, assume the admin role at label ADMIN_LOW, and edit the rules file with the Admin Editor action.

2. To use a Trusted Solaris-specific value for the version keyword:

   For the installed option, the version keyword.

   version - A version name, such as Trusted_Solaris_8, or the special word any. If any is used, any Trusted Solaris or SunOS release is matched.

   For the osname option, the version keyword.

   version -- A version of Trusted Solaris the Trusted Solaris environment installed on the system: for example, Trusted Solaris 7.

Validate a Rules File

1. In the admin role at label ADMIN_LOW, run the check script.

Copy a Rules File

1. In the admin role at label ADMIN_LOW, copy the file.