Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 9/10 Installation Guide: Network-Based Installations |
Part I Planning to Install Over the Network
1. Where to Find Solaris Installation Planning Information
2. Preconfiguring System Configuration Information (Tasks)
Advantages of Preconfiguring System Configuration Information
Preconfiguring With the sysidcfg File
To Create a sysidcfg Configuration File
Syntax Rules for the sysidcfg File
3. Preconfiguring With a Naming Service or DHCP
Part II Installing Over a Local Area Network
4. Installing From the Network (Overview)
5. Installing From the Network With DVD Media (Tasks)
6. Installing From the Network With CD Media (Tasks)
7. Patching the Miniroot Image (Tasks)
8. Installing Over the Network (Examples)
9. Installing From the Network (Command Reference)
Part III Installing Over a Wide Area Network
11. Preparing to Install With WAN Boot (Planning)
12. Installing With WAN Boot (Tasks)
13. SPARC: Installing With WAN Boot (Tasks)
14. SPARC: Installing With WAN Boot (Examples)
You can use the Power Management software that is provided in the Solaris OS to automatically save the state of a system and turn it off after it is idle for 30 minutes. When you install the current Solaris release on a system that complies with version 2 of the EPA's Energy Star guidelines, for example a Sun4U system, the Power Management software is installed by default. If you install with the Solaris installation program GUI, the installation program prompts you to enable or disable the Power Management software. The Solaris text installer prompts you to enable or disable the Power Management software after the installation is complete and the system reboots.
Note - If your system has Energy Star version 3 or later, you are not prompted for this information.
If you are performing interactive installations, you cannot preconfigure the Power Management information and avoid the prompt. However, by using a custom JumpStart installation, you can preconfigure the Power Management information by using a finish script to create an /autoshutdown or /noautoshutdown file on the system. When the system reboots, the /autoshutdown file enables Power Management and the /noautoshutdown file disables Power Management.
For example, the following line in a finish script enables the Power Management software and prevents the display of the prompt after the system reboots.
touch /a/autoshutdown
Finish scripts are described in Creating Finish Scripts in Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations.