x86: Booting a System (Task Map)
|
Header |
Header |
Header |
|---|---|---|
|
Boot an x86 based system to run level 3. |
Boot to run level 3. Used after shutting down the system or performing some system hardware maintenance task. | |
|
Boot an x86 based system to single-user mode. |
Boot to run level S. Used after performing a system maintenance task such as backing up a file system. |
x86: How to Boot a System to Run Level S (Single-User Level) |
|
Boot an x86 based system interactively. |
Boot interactively. Used after making temporary changes to a system file or the kernel for testing purposes. | |
|
Boot an x86 based system from the network. |
Used to boot a PXE or non-PXE device from the network with the default network configuration strategy. This method is used for booting a diskless client. | |
|
Solaris 10: Use the Device Configuration Assistant on an Oracle Solaris x86 based system. Note – Starting with the Solaris 10 1/06 release, the Device Configuration Assistant has been replaced by the GRUB menu. |
Used after changing the hardware configuration of the system. This utility enables you to boot the Solaris system from a different boot device, configure new or incorrectly configured hardware, or perform other device-related or boot-related tasks. | |
|
Boot a system for recovery purposes. |
Used to boot the system when a damaged file is preventing the system from booting. You might need to do one or both of the following to boot for recovery purposes: |
x86: How to Stop a System for Recovery Purposes |
|
Boot the system with the kernel debugger (kmdb). |
Used to troubleshooting system problems | |
|
Troubleshoot boot problems on systems that have 64-bit computing capabilities. |
If you have hardware that requires the system to load one or more device drivers that are not available in 64-bit mode, booting the system to 64-bit mode could fail. You would then need to boot the system to 32-bit mode. |
- © 2010, Oracle Corporation and/or its affiliates