Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Installation Guide: Live Upgrade and Upgrade Planning Oracle Solaris 10 8/11 Information Library |
Part I Upgrading With Live Upgrade
1. Where to Find Oracle Solaris Installation Planning Information
4. Using Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Live Upgrade (Tasks)
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Live Upgrade Boot Environments (Tasks)
Overview of Live Upgrade Maintenance
Displaying the Status of All Boot Environments
To Display the Status of All Boot Environments
Updating a Previously Configured Boot Environment
To Update a Previously Configured Boot Environment
Deleting an Inactive Boot Environment
To Delete an Inactive Boot Environment
Displaying the Name of the Active Boot Environment
To Display the Name of the Active Boot Environment
Changing the Name of a Boot Environment
To Change the Name of an Inactive Boot Environment
Adding or Changing a Description Associated With a Boot Environment Name
To Add or Change a Description for a Boot Environment Name With Text
To Add or Change a Description for a Boot Environment Name With a File
To Determine a Boot Environment Name From a Text Description
To Determine a Boot Environment Name From a Description in a File
To Determine a Boot Environment Description From a Name
Viewing the Configuration of a Boot Environment
To View the Configuration of a Boot Environment
8. Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed
10. Live Upgrade (Command Reference)
Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool
11. Live Upgrade and ZFS (Overview)
12. Live Upgrade for ZFS (Planning)
13. Creating a Boot Environment for ZFS Root Pools
14. Live Upgrade For ZFS With Non-Global Zones Installed
B. Additional SVR4 Packaging Requirements (Reference)
A boot environment's scheduled creation, upgrade, or copy job can be canceled just prior to the time the job starts. The job can be scheduled by the lumake command. At any time, only one job can be scheduled on a system.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# lucancel
The job no longer executes at the time that is specified.