42        On SPARC based systems, the bootstrap procedure on most machines
  43        consists of the following basic phases.
  44 
  45 
  46        After the machine is turned on, the system firmware (in PROM) executes
  47        power-on self-test (POST). The form and scope of these tests depends on
  48        the version of the firmware in your system.
  49 
  50 
  51        After the tests have been completed successfully, the firmware attempts
  52        to autoboot if the appropriate flag has been set in the non-volatile
  53        storage area used by the firmware. The name of the file to load, and
  54        the device to load it from can also be manipulated.
  55 
  56 
  57        These flags and names can be set using the eeprom(1M) command from the
  58        shell, or by using PROM commands from the ok prompt after the system
  59        has been halted.
  60 
  61 
  62        The second level program is either a fileystem-specific boot block
  63        (when booting from a disk), or inetboot (when booting across the
  64        network).
  65 
  66 
  67        Network Booting
  68 
  69 
  70        Network booting occurs in two steps: the client first obtains an IP
  71        address and any other parameters necessary to permit it to load the
  72        second-stage booter.  The second-stage booter in turn loads the boot
  73        archive from the boot device.
  74 
  75 
  76        An IP address can be obtained in one of three ways: RARP, DHCP, or
  77        manual configuration, depending on the functions available in and
  78        configuration of the PROM. Machines of the sun4u and sun4v kernel
  79        architectures have DHCP-capable PROMs.
  80 
  81 
  82        The boot command syntax for specifying the two methods of network

  42        On SPARC based systems, the bootstrap procedure on most machines
  43        consists of the following basic phases.
  44 
  45 
  46        After the machine is turned on, the system firmware (in PROM) executes
  47        power-on self-test (POST). The form and scope of these tests depends on
  48        the version of the firmware in your system.
  49 
  50 
  51        After the tests have been completed successfully, the firmware attempts
  52        to autoboot if the appropriate flag has been set in the non-volatile
  53        storage area used by the firmware. The name of the file to load, and
  54        the device to load it from can also be manipulated.
  55 
  56 
  57        These flags and names can be set using the eeprom(1M) command from the
  58        shell, or by using PROM commands from the ok prompt after the system
  59        has been halted.
  60 
  61 
  62        The second level program is either a filesystem-specific boot block
  63        (when booting from a disk), or inetboot (when booting across the
  64        network).
  65 
  66 
  67        Network Booting
  68 
  69 
  70        Network booting occurs in two steps: the client first obtains an IP
  71        address and any other parameters necessary to permit it to load the
  72        second-stage booter.  The second-stage booter in turn loads the boot
  73        archive from the boot device.
  74 
  75 
  76        An IP address can be obtained in one of three ways: RARP, DHCP, or
  77        manual configuration, depending on the functions available in and
  78        configuration of the PROM. Machines of the sun4u and sun4v kernel
  79        architectures have DHCP-capable PROMs.
  80 
  81 
  82        The boot command syntax for specifying the two methods of network