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

Contents of /xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.25 - (hide annotations) (download) (as text)
Tue Sep 11 22:49:20 2012 UTC (23 months, 2 weeks ago) by nightmorph
Branch: MAIN
Changes since 1.24: +25 -8 lines
File MIME type: application/xml
update handbooks for initramfs changes needed for separate /usr and other partitions. bug #415175, bug #434550, bug #434554, bug #434732

1 swift 1.1 <?xml version='1.0' encoding='UTF-8'?>
2     <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3    
4     <!-- The content of this document is licensed under the CC-BY-SA license -->
5 neysx 1.16 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 swift 1.1
7 nightmorph 1.25 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-bootloader.xml,v 1.24 2011/05/09 19:47:22 nightmorph Exp $ -->
8 swift 1.1
9     <sections>
10 swift 1.9
11 nightmorph 1.25 <version>12</version>
12     <date>2012-09-11</date>
13 swift 1.9
14 swift 1.1 <section>
15     <title>Making your Choice</title>
16     <subsection>
17     <title>Introduction</title>
18     <body>
19    
20     <p>
21     Now that your kernel is configured and compiled and the necessary system
22     configuration files are filled in correctly, it is time to install a
23     program that will fire up your kernel when you start the system. Such a
24     program is called a <e>bootloader</e>.
25     </p>
26    
27     <p>
28     Several bootloaders exist for Linux/Alpha. You must choose one of the supported
29     bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri>
30     and <uri link="#milo">MILO</uri>.
31     </p>
32    
33     </body>
34     </subsection>
35     </section>
36     <section id="aboot">
37     <title>Default: Using aboot</title>
38     <body>
39    
40 nightmorph 1.18 <note>
41     <c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b>
42     partitions.
43     </note>
44    
45 swift 1.1 <p>
46     We first install aboot on our system. Of course we use <c>emerge</c> to
47     do so:
48     </p>
49    
50 jkt 1.17 <pre caption="Installing aboot">
51 nightmorph 1.19 # <i>emerge aboot</i>
52 swift 1.1 </pre>
53    
54     <p>
55     The next step is to make our bootdisk bootable. This will start
56     <c>aboot</c> when you boot your system. We make our bootdisk bootable by
57     writing the <c>aboot</c> bootloader to the start of the disk.
58     </p>
59    
60 jkt 1.17 <pre caption="Making your bootdisk bootable">
61 swift 1.1 # <i>swriteboot -f3 /dev/sda /boot/bootlx</i>
62     # <i>abootconf /dev/sda 2</i>
63     </pre>
64    
65     <note>
66     If you use a different partitioning scheme than the one we use
67     throughout this chapter, you have to change the commands accordingly.
68     Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
69 swift 1.14 <c>man 8 abootconf</c>). Also, if your root filesystem is ran using the JFS
70     filesystem, make sure it gets mounted read-only at first by adding <c>ro</c> as
71     a kernel option.
72 swift 1.1 </note>
73    
74     <p>
75 nightmorph 1.25 Although <c>aboot</c> is now installed, we still need to write a configuration
76     file for it. Aboot only requires one line for each configuration, so we
77     can do this:
78     </p>
79    
80     <pre caption="Creating /etc/aboot.conf">
81     # <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' &gt; /etc/aboot.conf</i>
82    
83     <comment>
84     If, while building the Linux kernel, you opted to include an initramfs to boot
85     from, then you will need to change the configuration by referring to this
86     initramfs file and telling the initramfs where your real root device is at:
87     </comment>
88    
89     # <i>echo '0:2/boot/vmlinux.gz initrd=/boot/<keyval id="genkernel-initrd"/> real_root=/dev/sda2' &gt; /etc/aboot.conf</i>
90     </pre>
91    
92    
93     <p>
94     Additionally, you can make Gentoo boot automatically by setting up some SRM
95     variables. You can try setting these variables from Linux, but it may be easier
96     to do so from the SRM console itself.
97 swift 1.1 </p>
98    
99 jkt 1.17 <pre caption="Automatically booting Gentoo">
100 vapier 1.6 # <i>cd /proc/srm_environment/named_variables</i>
101     # <i>echo -n 0 &gt; boot_osflags</i>
102     # <i>echo -n '' &gt; boot_file</i>
103 vapier 1.7 # <i>echo -n 'BOOT' &gt; auto_action</i>
104 vapier 1.6 # <i>echo -n 'dkc100' &gt; bootdef_dev</i>
105     <comment>(Substitute dkc100 with whatever your boot device is)</comment>
106 swift 1.1 </pre>
107    
108     <p>
109 vapier 1.5 If you need to get into the SRM console again in the future (to recover
110     your Gentoo install, play with some variables, or whatever), just hit
111     CTRL+C to abort the automatic loading process.
112     </p>
113    
114     <p>
115     If you're installing using a serial console, don't forget to include
116     the serial console boot flag in <path>aboot.conf</path>. See
117     <path>/etc/aboot.conf.example</path> for some further information.
118 swift 1.1 </p>
119    
120     <p>
121     Aboot is now configured and ready to use. Continue with <uri
122 swift 1.3 link="#reboot">Rebooting the System</uri>.
123 swift 1.1 </p>
124    
125     </body>
126     </section>
127     <section id="milo">
128     <title>Alternative: Using MILO</title>
129     <body>
130    
131     <p>
132     Before continuing, you should decide on how to use MILO. In this
133     section, we will assume that you want to make a MILO boot floppy. If you
134     are going to boot from an MS-DOS partition on your hard disk, you should
135     amend the commands appropriately.
136     </p>
137    
138     <p>
139     To install MILO, we use <c>emerge</c>.
140     </p>
141    
142 jkt 1.17 <pre caption="Installing MILO">
143 nightmorph 1.20 # <i>emerge milo</i>
144 swift 1.1 </pre>
145    
146     <p>
147     After MILO has been installed, the MILO images should be in
148     <path>/opt/milo</path>. The commands below make a bootfloppy for use
149     with MILO. Remember to use the correct image for your Alpha-system.
150     </p>
151    
152 jkt 1.17 <pre caption="Installing MILO on a floppy">
153 swift 1.1 <comment>(First insert a blank floppy)</comment>
154     # <i>fdformat /dev/fd0</i>
155     # <i>mformat a:</i>
156 nightmorph 1.23 # <i>mcopy /opt/milo/milo-2.4-18-gentoo-ruffian a:\milo</i>
157 nightmorph 1.22 # <i>mcopy /opt/milo/linload.exe a:\linload.exe</i>
158 swift 1.1 <comment>(Only if you have a Ruffian:</comment>
159     # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
160     <comment>)</comment>
161     # <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
162     </pre>
163    
164     <p>
165     Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
166     set environment variables in your ARCS Firmware to get MILO to start;
167     this is all explained in the <uri
168     link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples
169     on common systems, and examples of the commands to use in interactive mode.
170     </p>
171    
172     <p>
173     Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri>
174     is a <e>bad</e> idea.
175     </p>
176    
177     <p>
178 swift 1.3 Now continue with <uri link="#reboot">Rebooting the System</uri>.
179 swift 1.1 </p>
180    
181     </body>
182     </section>
183 cam 1.4 <section id="reboot">
184 swift 1.3 <title>Rebooting the System</title>
185     <subsection>
186     <body>
187    
188     <p>
189     Exit the chrooted environment and unmount all mounted partitions. Then type in
190     that one magical command you have been waiting for: <c>reboot</c>.
191     </p>
192    
193     <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
194     # <i>exit</i>
195 swift 1.8 cdimage ~# <i>cd</i>
196 nightmorph 1.24 cdimage ~# <i>umount -l /mnt/gentoo/dev{/shm,/pts,}</i>
197     cdimage ~# <i>umount -l /mnt/gentoo{/boot,/proc,}</i>
198 swift 1.3 cdimage ~# <i>reboot</i>
199     </pre>
200    
201     <p>
202     Of course, don't forget to remove the bootable CD, otherwise the CD will be
203     booted again instead of your new Gentoo system.
204     </p>
205    
206     <p>
207     Once rebooted in your Gentoo installation, finish up with <uri
208     link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
209     </p>
210    
211     </body>
212     </subsection>
213     </section>
214    
215 swift 1.1 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20