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

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