summaryrefslogtreecommitdiff
path: root/en/boot-installer/mips.xml
blob: fe63cdd0d665b1485c05d284872ef9fb2b4a070a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->


  <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>

   <sect3>
   <title>SGI TFTP Booting</title>
<para>

After entering the command monitor use

<informalexample><screen>
bootp():
</screen></informalexample>

on SGI machines to boot linux and to begin installation of the &debian;
Software.  In order to make this
work you may have to unset the <envar>netaddr</envar> environment
variable. Type

<informalexample><screen>
unsetenv netaddr
</screen></informalexample>

in the command monitor to do this.

</para>
  </sect3>

  </sect2>

  <sect2 arch="mips"><title>Boot Parameters</title>

   <sect3>
   <title>SGI TFTP Booting</title>
<para>

On SGI machines you can append boot parameters to the
<command>bootp():</command> command in the command monitor.

</para><para>

Following the <command>bootp():</command> command you can give the
path and name of the file to boot if you did not give an explicit name
via your bootp/dhcp server. Example:

<informalexample><screen>
bootp():/boot/tftpboot.img
</screen></informalexample>

Further kernel parameters can be passed via <command>append</command>:

<informalexample><screen>
bootp(): append="root=/dev/sda1"
</screen></informalexample>

</para>
  </sect3>

  </sect2>