|
271.
|
|
|
OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1830
|
|
272.
|
|
|
To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1838
|
|
273.
|
|
|
If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1850
|
|
274.
|
|
|
You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend="device-names"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1863
|
|
275.
|
|
|
Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form: <informalexample> <screen> ![](/@@/translation-newline)
<replaceable>driver-name</replaceable>@ ![](/@@/translation-newline)
<replaceable>unit-address</replaceable>: ![](/@@/translation-newline)
<replaceable>device-arguments</replaceable> ![](/@@/translation-newline)
</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1873
|
|
276.
|
|
|
To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen> ![](/@@/translation-newline)
# echo disk1:1 > /proc/openprom/options/boot-device ![](/@@/translation-newline)
</screen></informalexample> and under Solaris:
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1896
|
|
277.
|
|
|
eeprom boot-device=disk1:1
|
|
|
Tag: screen
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1915
|
|
278.
|
|
|
BIOS Setup
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1925
|
|
279.
|
|
|
In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1926
|
|
280.
|
|
|
Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
preparing.xml:1938
|