System Initialization (Sparc): Difference between revisions
| [unchecked revision] | [unchecked revision] |
m (replaced unintentional deletion) |
|||
| Line 11: | Line 11: | ||
== Network == |
== Network == |
||
Loading from the network uses RARP to configure an IP address. It then connects to the TFTP server on the machine that responded to the RARP request, and downloads a file whose name is the machine's IP address in hex (with ". |
Loading from the network uses RARP to configure an IP address. It then connects to the TFTP server on the machine that responded to the RARP request, and downloads a file whose name is the machine's IP address in hex (with ".SUN4C" or ".SUN4M" appended if it's a V7 or V8 SPARC, respectively). This is then used as the bootloader. |
||
== See Also == |
== See Also == |
||
Revision as of 22:29, 7 March 2010
At boot time, a SPARC system will load the OpenBoot firmware, which then initializes basic hardware (such as the framebuffer, serial ports, keyboard, and disks), tests system functioning, and, optionally, (if the auto-boot? option is set to true) loads a primary bootloader in some way. Otherwise, it gives the user an "ok" prompt, at which to type initialization commands or FORTH instructions.
In theory, one could load an operating system from any device they wish, regardless of whether the device is directly supported by OpenBoot (eg, by typing in FORTH words to stick the raw bytes of the operating system code in memory). In parctice, however, an operating system is generally loaded from the hard disk, a floppy, or the network.
Hard disk
Typing "boot disk" at the boot prompt loads a bootloader from the hard disk, starting with sector 1 (512 bytes from the beginning of the disk) and continuing for 15 more sectors (7.5 Kb), assuming that the disk has a proper Sun Disklabel on it. Alternatively, "load disk" loads the bootloader into memory but does not load it.
Floppy
Somebody who has tried this, please fill this in. Theoretically, because disk-label provides the load command, it should work the same way, but who knows?
Network
Loading from the network uses RARP to configure an IP address. It then connects to the TFTP server on the machine that responded to the RARP request, and downloads a file whose name is the machine's IP address in hex (with ".SUN4C" or ".SUN4M" appended if it's a V7 or V8 SPARC, respectively). This is then used as the bootloader.