Insert the Trusted Solaris Device Assistant diskette into the floppy drive.
Choose the install choice of booting from a CDROM.
Insert the Trusted Solaris CDROM in the CD drive.
Turn on the system components in the order recommended in the hardware guide.
If the workstation starts booting, press L1-A or Stop-A.
If the screen displays the > prompt, enter n and press Return to display the ok prompt.
Enter the following commands:
$ su root # halt |
If the screen displays the > prompt, enter n and press Return to display the ok prompt.
Shut Down the workstation from the TP menu.
If the screen displays the > prompt, enter n and press Return to display the ok prompt.
See "Plan Workstation Hardware and Capacity." for hardware, disk space, and memory requirements.
See your hardware manual, such as the Solaris 7 8/99 Sun Hardware Platform Guide for instructions.
Place the Trusted Solaris CD in the workstation's CDROM drive.
Boot the workstation:
boot cdrom |
Use the command
boot sd(0,6,2) |
If you are booting from CDROM and with a custom JumpStart diskette, enter:
boot cdrom - install |
A space is required between the minus sign and install.
To install from a server on the network, enter:
boot net |
To install from a server on the network for a custom JumpStart installation, enter:
boot net - install |
A space is required between the minus sign and install.
After you type the boot command, the workstation goes through a booting phase where hardware and system components are checked. The following screen provides an example of what you see.
Type b (boot), c (continue), or n (new command mode) >n Type help for more information ok boot cdromRebooting with command: cdrom Boot device: /sbus/esp@0, 8000000/sd@6, 0:c File and args: SunOS Release 5.7 Version Trusted_Solaris_7 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1999, Sun Microsystems, Inc. WARNING: clock gained 35 days -- CHECK AND RESET THE DATE! Configuring the /devices directory Configuring the /dev directory Starting OpenWindows... |
The following screen provides an example of a custom JumpStart booting sequence.
Type b (boot), c (continue), or n (new command mode) >n Type help for more information ok boot net - installBooting from: le(0,0,0) - install 2bc00 hostname: sora domainname: aviary.eco.org root server: grebe root directory: /export/install/trusted_solaris_7_sparc/s0/export/exec/kvm/sparc.sun4c.Trust ed Solaris_7 SunOS Release 5.7 Version Trusted_Solaris_7 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1999, Sun Microsystems, Inc. Configuring the /devices directory Configuring the /dev directory Searching for JumpStart directory...using heron:/jumpstart Starting OpenWindows... |
The booting phase will last for a few minutes.
The Welcome to Trusted Solaris screen briefly appears, then the screen turns blue-gray and a Trusted Solaris Install Console is displayed in the upper left corner. Messages display in the console during installation.
The Trusted Solaris installation program is running.
If you are installing from a Trusted Solaris CDROM, the program guides you step by step through installing Trusted Solaris software; it also has online help to answer your questions.
If you have correctly set up a custom JumpStart installation, you are not prompted for information.
If you have correctly set up a network installation, you will be prompted for information after system identification is completed.
See Appendix D, Example Worksheets for sample answers.
Select a language and a locale
--------- System identification starts here---------
Name of workstation
Is it networked?
Its primary network interface
Its IP address
Its Name Service [None for the NIS+ root master] [NIS+ for clients]
Do not choose the options Other or NIS; they do not work in the Trusted Solaris environment.
On a subnet?
Its subnet mask
Time zone
Date and time
--------- System identification completed ---------
--------- Searches for JumpStart scripts appear in the upper left console window ---------
Upgrade is not supported.
Allocate client services?
Allocate client services if the workstation will serve diskless clients.
For performance reasons, your NIS+ master should not serve diskless clients.
Diskless clients are installed using the Host Manager in the Solstice_Apps folder. See Chapter 10, Configuring Diskless Clients.
Select the languages that can be displayed onscreen.
Software group
The groups Core and End User are identical in the Trusted Solaris environment.
Select To Include Solaris 64-bit support
The 64-bit system will be installed, but your system will boot 32-bit if the Flash PROM needs to be upgraded.
See "Updating the Flash PROM on the Ultra 1, Ultra 2, Ultra 450, and Sun Enterprise 450 Systems" in Solaris 7 8/99 Sun Hardware Platform Guide for how to upgrade the Flash PROM. You do not need to install the Solaris 7 environment for the PROM upgrade; install the Trusted Solaris 7 environment.
Customize the installation?
Disks to use.
Preserve the format of any of the disks?
Auto-layout file system?
Which file systems to auto-layout?
Customize the size of the partitions? YES, see "Disk Partitioning Hints".
Begin installation.
Reboot?
After you provide the requested information to the installation program, the actual installation takes from 30 to 60 minutes. The speed of your medium: CDROM, diskette, or net, determines the installation time.
-- Create at least one audit partition named /etc/security/audit/workstation_name.
-- Create sufficient swap space.
-- Swap space that is double the size of the workstation's memory is a good rule of thumb.
-- Create an /export/home partition large enough for the users' home directories.
-- Create a small /export partition to hold some temporary configuration files. It also serves as a mount point.
-- Allocate enough space for the clients' root and swap. See the sample worksheet, "OS Server Installation Program Example"
When you install an OS server, you allocate the disk space that is required for the clients that that server will support. Then, after the OS server is installed, you configure the clients (Chapter 10, Configuring Diskless Clients).
Before reboot, the install log is in /tmp/install_log. After reboot, the install log is in /var/sadm/system/logs/install_log.
Look for successful installation of packages.
Ignore messages of the form:
WARNING: quick verify of filename; wrong mod time.
The workstation must have a root password in order for the root role to work. The root role is required for successful configuration.
Choose a root password by answering the password prompts.
Root password: rootpassword Re-enter your root password: rootpassword |
Do not forget the root password. The software cannot be configured without it.
If you manually reboot your system, type:
# halt ok boot disk |
Then enter a root password at the prompt.
Users must not disclose their passwords to another person, as that person may then have access to the data of the user and will not be uniquely identified or accountable. Note that disclosure can be direct, through the user deliberately disclosing her/his password to another person, or indirect, e.g. through writing it down, or choosing an insecure password. Trusted Solaris provides protection against insecure passwords, but cannot prevent a user disclosing her/his password or writing it down.
Errors you encounter during installation are described and debugged in the Troubleshooting section of the Solaris 7 Installation Collection (see http://docs.sun.com/ab2/coll.241.4).
If you installed an OS Server system type, allocated space for diskless clients, and selected the initial installation option, you are not finished.
Use the Host Manager to complete the setup of these clients, as described in Chapter 10, Configuring Diskless Clients.
The Trusted Solaris installation program only allocates space for clients during an initial installation. The Host Manager completes client setup by providing their required directories.
For pointers to administration books, see Chapter 11, Where to Find....
Check that all Trusted Solaris configuration tasks are complete.
For an overview of individual workstation configuration tasks, see Chapter 6, Configuring a NIS+ Client.