source: BOOK/bootable/mips/colo.xml @ 0cdf4ac

clfs-1.2clfs-2.1clfs-3.0.0-systemdclfs-3.0.0-sysvinitsystemdsysvinit
Last change on this file since 0cdf4ac was 0cdf4ac, checked in by Chris Staub <chris@…>, 18 years ago

More text updates

  • Property mode set to 100644
File size: 2.1 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4  <!ENTITY % general-entities SYSTEM "../../general.ent">
5  %general-entities;
6]>
7
8<sect1 id="ch-bootable-colo">
9  <?dbhtml filename="colo.html"?>
10
11  <title>Making the CLFS System Bootable via Colo</title>
12
13  <indexterm zone="ch-bootable-colo">
14    <primary sortas="a-Colo">Colo</primary>
15    <secondary>configuring</secondary>
16  </indexterm>
17
18  <note os="a">
19    <para>This bootloader is for the MIPS based cobalt servers RaQ,
20    RaQ2, Qube, or the Qube2.</para>
21  </note>
22
23  <para os="c">Your shiny new CLFS system is almost complete. One of the last
24  things to do is ensure you can boot it. The instructions below apply
25  only to Cobalt RaQ1/RaQ2/Cube2 servers. Information on <quote>boot
26  loading</quote> for other architectures should be available in the
27  usual resource-specific locations for those architectures.</para>
28
29  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
30  href="../x86/grub.xml"
31  xpointer="xpointer(//*[@os='b'])"/>
32
33  <para os="d">Earlier, we compiled and installed the Cobalt boot loader
34  software in preparation for this step. Now we will configure our system
35  to boot using Colo. Here is a simple <filename>default.colo</filename>
36  to use.</para>
37
38<screen><userinput>cat &gt; /boot/default.colo &lt;&lt; "EOF"
39<literal>#:CoLo:#
40#
41# load linux
42#
43lcd 'Booting &linux-version;...'
44load vmlinux-&linux-version;.gz
45execute root=/dev/hda2 console=ttyS0,115200 ide1=noprobe</literal>
46EOF</userinput></screen>
47
48  <para os="e">Included in <filename class="directory">/usr/lib/colo/examples</filename>
49  are more examples of a <filename>default.colo</filename> file.</para>
50
51  <para os="v">The FHS stipulates that the bootloader's configuration file should
52  be symlinked to <filename class="symlink">/etc/{Bootloader Name}</filename>.
53  To satisfy this requirement for Colo, issue the following command:</para>
54
55<screen os="f"><userinput>mkdir -v /etc/colo &amp;&amp;
56ln -sv /boot/colo/default.colo /etc/colo</userinput></screen>
57
58</sect1>
Note: See TracBrowser for help on using the repository browser.