/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.17 Revision 1.18
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.17 2007/02/07 15:12:43 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.18 2007/05/07 18:11:41 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>7.1</version> 11<version>8.0</version>
12<date>2007-02-08</date> 12<date>2007-05-07</date>
13 13
14<section id="sgi"> 14<section id="sgi">
15<title>Silicon Graphics Machines -- Setting Up arcload</title> 15<title>Silicon Graphics Machines -- Setting Up arcload</title>
16<subsection> 16<subsection>
17<title>Which one?</title> 17<title>Which one?</title>
134 } 134 }
135} 135}
136</pre> 136</pre>
137 137
138<p> 138<p>
139Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may 139Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may reside
140reside either in the volume header, or on an EXT2/3 partition. If you wish to 140either in the volume header, or on a partition. If you wish to utilise this
141utilise this newer feature, you may instead place the files in your 141newer feature, you may instead place the files in your <path>/boot</path>
142<path>/boot</path> partition (or <path>/</path> if your boot partition is not 142partition (or <path>/</path> if your boot partition is not separate).
143separate). 143<c>arcload</c> uses the filesystem driver code from the popular <c>grub</c>
144bootloader, and thus supports the same range of filesystems.
144</p> 145</p>
145 146
146<pre caption="Placing arc.cf and kernel in the volume header"> 147<pre caption="Placing arc.cf and kernel in the volume header">
147# <i>dvhtool --unix-to-vh arc.cf arc.cf</i> 148# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
148# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i> 149# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
171</p> 172</p>
172 173
173<ul> 174<ul>
174 <li> 175 <li>
175 There's a 675kB (approximate) limit on kernels. The current size of Linux 176 There's a 675kB (approximate) limit on kernels. The current size of Linux
176 2.4 makes it damn near impossible to make a kernel this size. Linux 2.6 is 177 2.4 makes it nearly impossible to make a kernel this size. Linux 2.6 is
177 totally out of the question. 178 totally out of the question.
178 </li> 179 </li>
179 <li> 180 <li>
180 64-bit kernels are not supported by the stock firmware (although these are 181 64-bit kernels are not supported by the stock firmware (although these are
181 highly experimental on Cobalt machines at this time) 182 highly experimental on Cobalt machines at this time)
434<pre caption="Rebooting"> 435<pre caption="Rebooting">
435<comment>(Exit the chroot environment)</comment> 436<comment>(Exit the chroot environment)</comment>
436# <i>exit</i> 437# <i>exit</i>
437 438
438<comment>(Unmount the drives)</comment> 439<comment>(Unmount the drives)</comment>
439# <i>umount /gentoo/boot</i> 440# <i>umount /mnt/gentoo/boot</i>
440# <i>umount /gentoo</i> 441# <i>umount /mnt/gentoo</i>
441 442
442<comment>(Reboot)</comment> 443<comment>(Reboot)</comment>
443# <i>reboot</i> 444# <i>reboot</i>
444</pre> 445</pre>
445 446
550&gt;&gt; <i>setenv OSLoadFilename ip28(working)</i> 551&gt;&gt; <i>setenv OSLoadFilename ip28(working)</i>
551</pre> 552</pre>
552 553
553<p> 554<p>
554Starting with <c>arcload-0.5</c>, files no longer need to be placed in the 555Starting with <c>arcload-0.5</c>, files no longer need to be placed in the
555volume header -- they may be placed in an EXT2/3 partition instead. To tell 556volume header -- they may be placed in a partition instead. To tell
556<c>arcload</c> where to look for its configuration file and kernels, one must 557<c>arcload</c> where to look for its configuration file and kernels, one must
557set the <c>OSLoadPartition</c> PROM variable. The exact value here will depend 558set the <c>OSLoadPartition</c> PROM variable. The exact value here will depend
558on where your disk resides on the SCSI bus. Use the <c>SystemPartition</c> PROM 559on where your disk resides on the SCSI bus. Use the <c>SystemPartition</c> PROM
559variable as a guide -- only the partition number should need to change. 560variable as a guide -- only the partition number should need to change.
560</p> 561</p>

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.18

  ViewVC Help
Powered by ViewVC 1.1.20