This is the boot command syntax:
{0} ok boot [device-specifier] [arguments]
|
Because a device alias cannot be syntactically distinguished from the arguments, OpenBoot resolves this ambiguity as follows:
If the space-delimited word following boot on the command line begins with /, the word is a device-path and, thus, a device-specifier. Any text to the right of this device-specifier is included in arguments.
If the space-delimited word matches an existing device alias, the word is a device-specifier. Any text to the right of this device-specifier is included in arguments.
Otherwise, the appropriate default boot device is used, and any text to the right of boot is included in arguments.
Consequently, boot command lines have the following possible forms.
{0} ok boot
With this form, boot loads and executes the program specified by the default boot arguments from the default boot device.
{0} ok boot device-specifier
If boot has a single argument that either begins with the character / or is the name of a defined devalias, boot uses the argument as a device specifier. boot loads and executes the program specified by the default boot arguments from the specified device.
If boot has a single argument that neither begins with the character / nor is the name of a defined devalias, boot uses all of the remaining text as its arguments.
{0} ok boot arguments
boot loads and executes the program specified by the arguments from the default boot device.
{0} ok boot device-specifier arguments
If there are at least two space-delimited arguments, and if the first such argument begins with the character / or if it is the name of a defined devalias, boot uses the first argument as a device specifier and uses all of the remaining text as its arguments. boot loads and executes the program specified by the arguments from the specified device.
For all of the above cases, boot records the device that it uses in the bootpath property of the /chosen node. boot also records the arguments that it uses in the bootargs property of the /chosen node.
Device alias definitions vary from virtual machine to virtual machine. Use the devalias command (described in Create a Device Alias) to obtain the definitions of your virtual machine's aliases.
For a description of the boot sequence changes and instructions on how you can manage the boot pool by using the bootadm boot-pool, refer to the Oracle Solaris 11.3 documentation at https://docs.oracle.com/en/operating-systems/solaris.html
.
![]() | Caution - The Verified Boot policy setting of enforce does not allow the boot process to proceed if the OpenBoot use-nvramrc? variable is set to true. You can directly set the use-nvramrc? variable with the setenv command, or the variable is automatically set to true when you use the nvalias command. If you set the use-nvramrc? variable to false, you will not be able to create device aliases with the nvalias command. For further details, refer to https://docs.oracle.com/cd/E37444_01/html/E37446/z40001291613819.html. |