|
67.
|
|
|
At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>
>>> boot dva0 -flags 0
</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>
>>> show dev
</screen></informalexample> to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, <command>-flags</command> argument is ignored, so you can just type <command>boot dva0</command>. If everything works OK, you will eventually see the Linux kernel boot.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:386
|
|
68.
|
|
|
If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>
>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
</screen></informalexample> (typed on one line), substituting, if necessary, the actual SRM boot device name for <filename>dva0</filename>, the Linux boot device name for <filename>fd0</filename>, and the desired kernel parameters for <filename>arguments</filename>.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:403
|
|
69.
|
|
|
If you want to specify kernel parameters when booting via <command>MILO</command>, you will have to interrupt bootstrap once you get into MILO. See <xref linkend="booting-from-milo"/>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:415
|
|
70.
|
|
|
Booting from Floppies with the ARC or AlphaBIOS Console
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:425
|
|
71.
|
|
|
In the OS Selection menu, set <command>linload.exe</command> as the boot loader, and <command>milo</command> as the OS Path. Bootstrap using the newly created entry.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:427
|
|
72.
|
|
|
Booting with MILO
|
|
|
Tag: title
|
|
|
|
Aviar amb MILO
|
|
Translated and reviewed by
Yannig MARCHEGAY (Kokoyaya)
|
|
|
|
Located in
boot-installer.xml:436
|
|
73.
|
|
|
MILO contained on the bootstrap media is configured to proceed straight to Linux automatically. Should you wish to intervene, all you need is to press space during MILO countdown.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:437
|
|
74.
|
|
|
If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: <informalexample><screen>
MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
</screen></informalexample> If you are booting from something other than a floppy, substitute <filename>fd0</filename> in the above example with the appropriate device name in Linux notation. The <command>help</command> command would give you a brief MILO command reference.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:443
|
|
75.
|
|
|
Booting from TFTP
|
|
|
Tag: title
|
|
|
|
Aviar a partir de TFTP
|
|
Translated and reviewed by
Yannig MARCHEGAY (Kokoyaya)
|
|
|
|
Located in
boot-installer.xml:462
|
|
76.
|
|
|
Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP).
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1595 boot-installer.xml:2080 boot-installer.xml:2597 boot-installer.xml:2706
|