SPARC: How to Boot a System to Run Level S (Single-User Level)

Use this procedure to boot a system that is currently at run level 0 to run level S.

1. Boot the system to run level S.

   ok boot -s

   
   

2. Type the superuser password when the following message is displayed.

   INIT: SINGLE USER MODE Type Ctrl-d to proceed with normal startup, (or give root password for system maintenance): xxx

   
   

3. Verify that the system is at run level S.

   # who -r . run-level S Jun 10 15:27 3 0

   
   

4. To bring the system up to multiuser state after you completed the system maintenance task, press Control-D.

SPARC: Example--Booting a System to Run Level S (Single-User Level)

The following example displays the messages from booting a system to run level S.

ok boot -s
.
.
.
Sun Microsystems Inc.   SunOS 5.9  Generic May 2002
Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
configuring IPv4 interfaces: hme0.
Hostname: starbug

INIT: SINGLE USER MODE

Type control-d to proceed with normal startup,
(or give root password for system maintenance): xxx
Sun Microsystems Inc.   SunOS 5.9  Generic May 2002
# who -r
   .       run-level S  Sep 19 08:49     S      0  ?
(Perform some maintenance task)
# Press Control-D

SPARC: How to Boot a System Interactively

Use this procedure to boot a system and you need to specify an alternate kernel or /etc/system file.

1. Boot the system interactively.

   ok boot -a

   
   

2. Answer the system prompts as described in the following table.

   System Prompt	Action
   Enter filename [kernel/[sparcv9]/unix]:	Provide the name of kernel to use for booting. Or, press Return to use the default kernel.
   Enter default directory for modules [/platform/`uname -i`/kernel /platform/`uname -m/kernel /kernel /usr/kernel]:	Provide an alternate path for the modules directory. Or, press Return to use the default kernel modules directory.
   Name of system file [etc/system]:	Provide the name of an alternate system file and press Return. Type /dev/null if your /etc/system file has been damaged. Or, press Return to use the default etc/system file.
   root filesystem type [ufs]:	Press Return to use the default root (/) file system. Type UFS for local disk booting, or NFS for network booting.
   Enter physical name of root device [physical_device_name]:	Provide an alternate device name and press Return. Or, press Return to use the default physical name of the root device.

3. If you are not prompted to answer the questions in the preceding table, verify that you typed the boot -a command correctly.

SPARC: Example--Booting a System Interactively

In the following example, the default choices (shown in square brackets []) are accepted.

ok boot -a
.
.
.
Rebooting with command: boot -a
Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0:a  File and args: -a
Enter filename [kernel/sparcv9/unix]: Press Return
Enter default directory for modules [/platform/SUNW,Ultra-5_10/kernel 
/platform/sun4u/kernel /kernel /usr/kernel]: Press Return
Name of system file [etc/system]: Press Return
SunOS Release 5.9 Version Generic 64-bit
Copyright (c) 1983-2002 by Sun Microsystems, Inc.
root filesystem type [ufs]: Press Return
Enter physical name of root device
[/pci@1f,0/pci@1,1/ide@3/disk@0,0:a]: Press Return
configuring IPv4 interfaces: hme0.
Hostname: starbug
The system is coming up.  Please wait.
checking ufs filesystems
.
.
.
The system is ready.
starbug console login:

SPARC: How to Boot a System From the Network

Any system can boot from the network if there is a boot server available. You might want to boot a standalone system from the network temporarily if the system cannot boot from the local disk. For information on changing or resetting the default boot device, see SPARC: How to Change the Default Boot Device.

Two network configuration boot strategies are available on sun4u systems:

• RARP (Reverse Address Resolution Protocol and ONC+ RPC Bootparams Protocol)

• DHCP (Dynamic Host Configuration Protocol)

The default network boot strategy is set to RARP. You can use either strategy depending on whether a RARP boot server or a DHCP boot server is available on your network.

Note - Sun Ultra systems must have PROM version 3.25.nn or later to use the DHCP network boot strategy. For information on finding your PROM version, see SPARC: How to Find the PROM Revision for a System.

If both methods are available, you can specify which service to use in the boot command temporarily. Or, you can save the network boot strategy across system reboots at the PROM level, by setting up an NVRAM alias. The following example uses the nvalias command to set up a network device alias for booting DHCP by default on a Sun Ultra 10 system.

ok nvalias net	 /pci@1f,4000/network@1,1:dhcp

This alias means that when you type boot net, the system boots by using the DHCP network book strategy.

Caution - You should not use the nvalias command to modify the NVRAMRC file unless you are very familiar with the syntax of this command and the nvunalias command. For information on using these commands, see the OpenBoot 3.x Command Reference Manual.

1. If necessary, shut down the system.

2. Determine the method for booting from the network and select one of the following:

   You must have already set up a RARP or DHCP boot server in your network to use either method to boot successfully.

   1. Boot the system from the network by using the DHCP method.

      ok boot net[:dhcp]

      
      

      If you have changed the PROM setting to boot DHCP by default, as in the preceding nvalias example, you only have to specify boot net.

   2. Boot the system from the network by using the RARP method.

      ok boot net[:rarp]

      
      

      Since RARP is the default network boot strategy, you only have to specify boot net:rarp if you have changed the PROM value to boot DHCP.