/[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.13 - (show annotations) (download) (as text)
Mon Mar 28 11:30:52 2005 UTC (9 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.12: +3 -3 lines
File MIME type: application/xml
Updating docos to 2005.0

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 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.0/hb-install-alpha-bootloader.xml,v 1.2 2005/03/28 08:20:02 swift Exp $ -->
8
9 <sections>
10
11 <version>2.00</version>
12 <date>2005-03-28</date>
13
14 <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 <p>
41 We first install aboot on our system. Of course we use <c>emerge</c> to
42 do so:
43 </p>
44
45 <pre caption = "Installing aboot">
46 # <i>emerge --usepkg aboot</i>
47 </pre>
48
49 <p>
50 The next step is to make our bootdisk bootable. This will start
51 <c>aboot</c> when you boot your system. We make our bootdisk bootable by
52 writing the <c>aboot</c> bootloader to the start of the disk.
53 </p>
54
55 <pre caption = "Making your bootdisk bootable">
56 # <i>swriteboot -f3 /dev/sda /boot/bootlx</i>
57 # <i>abootconf /dev/sda 2</i>
58 </pre>
59
60 <note>
61 If you use a different partitioning scheme than the one we use
62 throughout this chapter, you have to change the commands accordingly.
63 Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
64 <c>man 8 abootconf</c>).
65 </note>
66
67 <p>
68 Additionally, you can make Gentoo boot automatically by setting up the
69 aboot configuration file and some SRM variables. You can try setting
70 these variables from Linux, but it may be easier to do so from the SRM
71 console itself.
72 </p>
73
74 <pre caption = "Automatically booting Gentoo">
75 # <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' &gt; /etc/aboot.conf</i>
76 # <i>cd /proc/srm_environment/named_variables</i>
77 # <i>echo -n 0 &gt; boot_osflags</i>
78 # <i>echo -n '' &gt; boot_file</i>
79 # <i>echo -n 'BOOT' &gt; auto_action</i>
80 # <i>echo -n 'dkc100' &gt; bootdef_dev</i>
81 <comment>(Substitute dkc100 with whatever your boot device is)</comment>
82 </pre>
83
84 <p>
85 If you need to get into the SRM console again in the future (to recover
86 your Gentoo install, play with some variables, or whatever), just hit
87 CTRL+C to abort the automatic loading process.
88 </p>
89
90 <p>
91 If you're installing using a serial console, don't forget to include
92 the serial console boot flag in <path>aboot.conf</path>. See
93 <path>/etc/aboot.conf.example</path> for some further information.
94 </p>
95
96 <p>
97 Aboot is now configured and ready to use. Continue with <uri
98 link="#reboot">Rebooting the System</uri>.
99 </p>
100
101 </body>
102 </section>
103 <section id="milo">
104 <title>Alternative: Using MILO</title>
105 <body>
106
107 <p>
108 Before continuing, you should decide on how to use MILO. In this
109 section, we will assume that you want to make a MILO boot floppy. If you
110 are going to boot from an MS-DOS partition on your hard disk, you should
111 amend the commands appropriately.
112 </p>
113
114 <p>
115 To install MILO, we use <c>emerge</c>.
116 </p>
117
118 <pre caption = "Installing MILO">
119 # <i>emerge --usepkg milo</i>
120 </pre>
121
122 <p>
123 After MILO has been installed, the MILO images should be in
124 <path>/opt/milo</path>. The commands below make a bootfloppy for use
125 with MILO. Remember to use the correct image for your Alpha-system.
126 </p>
127
128 <pre caption = "Installing MILO on a floppy">
129 <comment>(First insert a blank floppy)</comment>
130 # <i>fdformat /dev/fd0</i>
131 # <i>mformat a:</i>
132 # <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
133 # <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
134 <comment>(Only if you have a Ruffian:</comment>
135 # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
136 <comment>)</comment>
137 # <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
138 </pre>
139
140 <p>
141 Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
142 set environment variables in your ARCS Firmware to get MILO to start;
143 this is all explained in the <uri
144 link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples
145 on common systems, and examples of the commands to use in interactive mode.
146 </p>
147
148 <p>
149 Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri>
150 is a <e>bad</e> idea.
151 </p>
152
153 <p>
154 Now continue with <uri link="#reboot">Rebooting the System</uri>.
155 </p>
156
157 </body>
158 </section>
159 <section id="reboot">
160 <title>Rebooting the System</title>
161 <subsection>
162 <body>
163
164 <p>
165 Exit the chrooted environment and unmount all mounted partitions. Then type in
166 that one magical command you have been waiting for: <c>reboot</c>.
167 </p>
168
169 <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
170 # <i>exit</i>
171 cdimage ~# <i>cd</i>
172 cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
173 cdimage ~# <i>reboot</i>
174 </pre>
175
176 <p>
177 Of course, don't forget to remove the bootable CD, otherwise the CD will be
178 booted again instead of your new Gentoo system.
179 </p>
180
181 <p>
182 Once rebooted in your Gentoo installation, finish up with <uri
183 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
184 </p>
185
186 </body>
187 </subsection>
188 </section>
189
190 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20