* [gentoo-doc-cvs] cvs commit: hb-install-mips-bootloader.xml
@ 2007-02-07 15:12 Xavier Neys
0 siblings, 0 replies; 3+ messages in thread
From: Xavier Neys @ 2007-02-07 15:12 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 07/02/07 15:12:44
Modified: hb-install-mips-bootloader.xml
Log:
#165769 arcload Installation Instruction Update
Revision Changes Path
1.17 xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?r1=1.16&r2=1.17
Index: hb-install-mips-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-mips-bootloader.xml 30 Aug 2006 22:52:28 -0000 1.16
+++ hb-install-mips-bootloader.xml 7 Feb 2007 15:12:43 -0000 1.17
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.16 2006/08/30 22:52:28 nightmorph Exp $ -->
+<!-- $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 $ -->
<sections>
-<version>7.0</version>
-<date>2006-08-30</date>
+<version>7.1</version>
+<date>2007-02-08</date>
<section id="sgi">
<title>Silicon Graphics Machines -- Setting Up arcload</title>
@@ -20,52 +20,9 @@
<p>
On SGI machines, we use the <c>arcload</c> boot loader. In previous releases,
we also provided <c>arcboot</c>, however it has been officially declared
-obsolete, in favour of <c>arcload</c>.
+obsolete, in favour of <c>arcload</c>.
</p>
-<!-- Slated for possible removal
-<table>
-<tr>
- <th> </th>
- <th>arcboot</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- It can load off EXT2 and EXT3 partitions, so no need to store them in the
- volume header
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- It doesn't work on Octane/Octane2, Origin 200/2000 or Indigo2 Impact
- (R10000)
- </ti>
-</tr>
-</table>
-
-<table>
-<tr>
- <th> </th>
- <th>arcload</th>
-</tr>
-<tr>
- <th>+</th>
- <ti>
- It boots ALL Linux-compatible SGI systems
- </ti>
-</tr>
-<tr>
- <th>-</th>
- <ti>
- Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels
- and config file to be placed in the volume header
- </ti>
-</tr>
-</table>
--->
-
<note>
The SGI volume header filenames are limited to 8 characters, and there may be
no more than 16 files contained in a single volume header.
@@ -74,146 +31,6 @@
</body>
</subsection>
-<!--<subsection>
-<title>Installing arcboot</title>
-<body>
-
-<warn>
-<c>arcboot</c> is deprecated and will be removed in future.
-</warn>
-
-<p>
-Previously in this guide, we showed you how to make a kernel, then copy it to
-the volume header using <c>dvhtool</c>. There were two main flaws with this
-system:
-</p>
-
-<ul>
- <li>This is not supported on all SGI systems</li>
- <li>It requires a significantly larger volume header</li>
-</ul>
-
-<p>
-In order to boot the machine, a bootloader, <c>arcboot</c> was developed for
-this purpose. Instead of putting the kernel directly into the volume header, we
-leave it in <path>/boot</path> (which resides on a EXT2/3 partition), and tell
-<c>arcboot</c> (which sits in the volume header in place of the kernel) where
-to find it. So our first step, is to emerge some tools that we'll use later...
-</p>
-
-<pre caption="Installing the required tools">
-# <i>emerge dvhtool arcboot</i>
-</pre>
-
-<p>
-That should have installed two tools, <c>arcboot</c> which sits in the volume
-header and loads kernels for us, and <c>dvhtool</c> which helps us put
-<c>arcboot</c> into the volume header.
-</p>
-
-<p>
-The <c>arcboot</c> binary lurks in <path>/usr/lib/arcboot</path>. The name of
-the binary depends on the machine it's compiled for.
-</p>
-
-<ul>
- <li>
- <c>arcboot.ip22</c>: The binary for Indy, Indigo2 (R4k) and Challenge S
- systems
- </li>
- <li>
- <c>arcboot.ip32</c>: The binary for O2 systems
- </li>
-</ul>
-
-<pre caption="Installing arcboot into the volume header">
-# <i>dvhtool - -unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i>
-</pre>
-
-<p>
-We then verify the presence of the file in the volume header.
-</p>
-
-<pre caption="Checking if arcboot made it okay">
-# <i>dvhtool - -print-volume-directory</i>
-- - - - - directory entries - - - - -
-Entry #0, name "linux", start 4, bytes 3262570
-Entry #1, name "newlinux", start 6377, bytes 7619627
-Entry #3, name "arcboot", start 21260, bytes 51448
-#
-</pre>
-
-<note>
-You'll notice that in the example above, there are two old kernels sitting
-around, <path>linux</path> and <path>newlinux</path>. This is a hangover from
-before we started using <c>arcboot</c>. Their presence doesn't matter - - just
-so long as <c>arcboot</c> is present, everything is fine.
-</note>
-
-<p>
-If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that
-<c>arcboot</c> employs a similar syntax in its configuration file. Bear in mind
-though; <c>arcboot</c> expects to find its configuration file existing on an
-EXT2/3 partition as <path>/etc/arcboot.conf</path>. The easiest way around this
-is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a
-file called <path>arcboot.conf</path> inside the <path>/boot/etc</path>
-directory. An example config can be found in
-<path>/etc/arcboot.conf.sample</path>.
-</p>
-
-<note>
-Adjust the paths accordingly if you don't have a separate <path>/boot</path>
-partition.
-</note>
-
-<pre caption="Putting arcboot.conf in its place">
-<comment>(Create the /boot/etc directory)</comment>
-# <i>mkdir /boot/etc</i>
-
-<comment>(Put our configuration into the target directory)</comment>
-# <i>cp /etc/arcboot.conf.sample /boot/etc/arcboot.conf</i>
-
-<comment>(Create a symlink back to /etc)</comment>
-# <i>ln -s /boot/etc/arcboot.conf /etc/arcboot.conf</i>
-
-<comment>(... and a symlink in /boot pointing to itself)</comment>
-# <i>(cd /boot; ln -s . boot)</i>
-</pre>
-
-<p>
-You can then edit <path>/etc/arcboot.conf</path> to your own preference. One
-possible layout, is to set up two kernel images: <path>new</path>, a freshly
-built image that may or may not work; and <path>working</path>, a proven
-trustworthy kernel image. The <path>arcboot.conf</path> for that setup looks a
-bit like this.
-</p>
-
-<pre caption="Example arcboot.conf">
-<comment># arcboot.conf</comment>
-<comment>#</comment>
-<comment># copyright 2002 Guido Guenther <agx@sigxcpu.org></comment>
-<comment>#</comment>
-<comment># known working version</comment>
-label=working
- image=/vmlinux
- append="root=/dev/sda3"
-
-<comment># fresh "untested" version</comment>
-label=new
- image=/vmlinux-new
- append="root=/dev/sda3"
-</pre>
-
-<p>
-Once that is set up, there's then just some little tweaks that you need to do
-within the SGI PROM to make this magic work. This is covered in, not the next
-section (that's for Cobalt servers) but the following section <uri
-link="#reboot">Rebooting the System</uri>.
-</p>
-
-</body>
-</subsection>
--->
<subsection>
<title>Installing arcload</title>
<body>
@@ -319,17 +136,13 @@
</pre>
<p>
-This is then placed in the volume header with <c>sash64</c> (or
-<c>sashARCS</c>) as shown below. Kernels also get placed in the volume header.
+Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may
+reside either in the volume header, or on an EXT2/3 partition. If you wish to
+utilise this newer feature, you may instead place the files in your
+<path>/boot</path> partition (or <path>/</path> if your boot partition is not
+separate).
</p>
-<note>
-With <c>arcload</c> 0.5, it is possible to load these files from an EXT3
-partition, rather than loading these into the volume header. If you are
-using the newer release, you may skip copying these to the volume
-header, and instead, place them in your <c>/boot</c> partition.
-</note>
-
<pre caption="Placing arc.cf and kernel in the volume header">
# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
@@ -597,7 +410,7 @@
<note>
<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI
-PROM so that it boots <!--<c>arcboot</c>/--><c>arcload</c> off disk and loads
+PROM so that it boots <c>arcload</c> off disk and loads
Linux.
This is not applicable to the setup of Cobalt servers. In fact, all your work
is done -- there is no configuration needed for the first boot up, you can skip
@@ -731,50 +544,35 @@
<pre caption="PROM settings for using arcload">
<comment>(Select arcload as the bootloader:- sash64 or sashARCS)</comment>
->> setenv OSLoader sash64
+>> <i>setenv OSLoader sash64</i>
<comment>(Use the "working" kernel image, defined in "ip28" section of arc.cf)</comment>
->> setenv OSLoadFilename ip28(working)
+>> <i>setenv OSLoadFilename ip28(working)</i>
</pre>
-</body>
-</subsection>
-
-<!-- Slated for removal
-<subsection>
-<title>Settings for arcboot</title>
-<body>
-
<p>
-<c>arcboot</c> loads its configuration file and kernels from your
-<path>/boot</path> partition, which needs to be formatted either EXT2 or EXT3.
-Thus <c>OSLoadPartition</c> needs to point to that partition. <c>OSLoader</c>
-should point to the <c>arcboot</c> binary in the volume header, and
-<c>OSLoadFilename</c> is the image name being used.
+Starting with <c>arcload-0.5</c>, files no longer need to be placed in the
+volume header -- they may be placed in an EXT2/3 partition instead. To tell
+<c>arcload</c> where to look for its configuration file and kernels, one must
+set the <c>OSLoadPartition</c> PROM variable. The exact value here will depend
+on where your disk resides on the SCSI bus. Use the <c>SystemPartition</c> PROM
+variable as a guide -- only the partition number should need to change.
</p>
-<pre caption="PROM settings for using arcboot">
-<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 - - sda1)</comment>
->> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i>
-
-<comment>(Use arcboot as the bootloader)</comment>
->> <i>setenv OSLoader arcboot</i>
-
-<comment>(Which boot image in arcboot.conf to load)</comment>
->> <i>setenv OSLoadFilename working</i>
-</pre>
+<note>
+Partitions are numbered starting at 0, not 1 as is the case in Linux.
+</note>
-<p>
-When testing kernels via <c>arcboot</c> you can specify an alternate image like
-so (where <c>new</c> is the alternate image):
-</p>
+<pre caption="Telling arcload where to find arc.cf">
+<comment>(If you wish to load from the volume header -- use partition 8)</comment>
+>> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
-<pre caption="Specifying an alternate image">
-# <i>boot new</i>
+<comment>(Otherwise, specify the partition and filesystem type)</comment>
+>> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)[ext2]</i>
</pre>
</body>
-</subsection> -->
+</subsection>
<subsection>
<title>All Done</title>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-doc-cvs] cvs commit: hb-install-mips-bootloader.xml
@ 2007-03-19 9:12 Josh Saddler
0 siblings, 0 replies; 3+ messages in thread
From: Josh Saddler @ 2007-03-19 9:12 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/03/19 09:12:08
Modified: hb-install-mips-bootloader.xml
Log:
language
Revision Changes Path
1.16 xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?r1=1.15&r2=1.16
Index: hb-install-mips-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- hb-install-mips-bootloader.xml 14 Mar 2007 06:24:40 -0000 1.15
+++ hb-install-mips-bootloader.xml 19 Mar 2007 09:12:08 -0000 1.16
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v 1.15 2007/03/14 06:24:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v 1.16 2007/03/19 09:12:08 nightmorph Exp $ -->
<sections>
-<version>7.1</version>
+<version>8.0</version>
<date>2007-02-08</date>
<section id="sgi">
@@ -173,7 +173,7 @@
<ul>
<li>
There's a 675kB (approximate) limit on kernels. The current size of Linux
- 2.4 makes it damn near impossible to make a kernel this size. Linux 2.6 is
+ 2.4 makes it nearly impossible to make a kernel this size. Linux 2.6 is
totally out of the question.
</li>
<li>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-doc-cvs] cvs commit: hb-install-mips-bootloader.xml
@ 2007-05-01 6:18 Josh Saddler
0 siblings, 0 replies; 3+ messages in thread
From: Josh Saddler @ 2007-05-01 6:18 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 07/05/01 06:18:51
Modified: hb-install-mips-bootloader.xml
Log:
mips bootloader updates, bug 176526
Revision Changes Path
1.17 xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?r1=1.16&r2=1.17
Index: hb-install-mips-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-mips-bootloader.xml 19 Mar 2007 09:12:08 -0000 1.16
+++ hb-install-mips-bootloader.xml 1 May 2007 06:18:51 -0000 1.17
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v 1.16 2007/03/19 09:12:08 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml,v 1.17 2007/05/01 06:18:51 nightmorph Exp $ -->
<sections>
<version>8.0</version>
-<date>2007-02-08</date>
+<date>2007-04-30</date>
<section id="sgi">
<title>Silicon Graphics Machines -- Setting Up arcload</title>
@@ -136,11 +136,12 @@
</pre>
<p>
-Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may
-reside either in the volume header, or on an EXT2/3 partition. If you wish to
-utilise this newer feature, you may instead place the files in your
-<path>/boot</path> partition (or <path>/</path> if your boot partition is not
-separate).
+Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may reside
+either in the volume header, or on a partition. If you wish to utilise this
+newer feature, you may instead place the files in your <path>/boot</path>
+partition (or <path>/</path> if your boot partition is not separate).
+<c>arcload</c> uses the filesystem driver code from the popular <c>grub</c>
+bootloader, and thus supports the same range of filesystems.
</p>
<pre caption="Placing arc.cf and kernel in the volume header">
@@ -436,8 +437,8 @@
# <i>exit</i>
<comment>(Unmount the drives)</comment>
-# <i>umount /gentoo/boot</i>
-# <i>umount /gentoo</i>
+# <i>umount /mnt/gentoo/boot</i>
+# <i>umount /mnt/gentoo</i>
<comment>(Reboot)</comment>
# <i>reboot</i>
@@ -552,7 +553,7 @@
<p>
Starting with <c>arcload-0.5</c>, files no longer need to be placed in the
-volume header -- they may be placed in an EXT2/3 partition instead. To tell
+volume header -- they may be placed in a partition instead. To tell
<c>arcload</c> where to look for its configuration file and kernels, one must
set the <c>OSLoadPartition</c> PROM variable. The exact value here will depend
on where your disk resides on the SCSI bus. Use the <c>SystemPartition</c> PROM
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-05-01 6:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-07 15:12 [gentoo-doc-cvs] cvs commit: hb-install-mips-bootloader.xml Xavier Neys
-- strict thread matches above, loose matches on Subject: below --
2007-03-19 9:12 Josh Saddler
2007-05-01 6:18 Josh Saddler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox