/[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.4 - (show annotations) (download) (as text)
Wed Aug 4 13:20:18 2004 UTC (10 years, 2 months ago) by cam
Branch: MAIN
Changes since 1.3: +2 -2 lines
File MIME type: application/xml
Typo, label is #reboot, not #rebooting

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/hb-install-alpha-bootloader.xml,v 1.3 2004/08/04 08:46:30 swift Exp $ -->
8
9 <sections>
10 <section>
11 <title>Making your Choice</title>
12 <subsection>
13 <title>Introduction</title>
14 <body>
15
16 <p>
17 Now that your kernel is configured and compiled and the necessary system
18 configuration files are filled in correctly, it is time to install a
19 program that will fire up your kernel when you start the system. Such a
20 program is called a <e>bootloader</e>.
21 </p>
22
23 <p>
24 Several bootloaders exist for Linux/Alpha. You must choose one of the supported
25 bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri>
26 and <uri link="#milo">MILO</uri>.
27 </p>
28
29 </body>
30 </subsection>
31 </section>
32 <section id="aboot">
33 <title>Default: Using aboot</title>
34 <body>
35
36 <p>
37 We first install aboot on our system. Of course we use <c>emerge</c> to
38 do so:
39 </p>
40
41 <pre caption = "Installing aboot">
42 # <i>emerge --usepkg aboot</i>
43 </pre>
44
45 <p>
46 The next step is to make our bootdisk bootable. This will start
47 <c>aboot</c> when you boot your system. We make our bootdisk bootable by
48 writing the <c>aboot</c> bootloader to the start of the disk.
49 </p>
50
51 <pre caption = "Making your bootdisk bootable">
52 # <i>swriteboot -f3 /dev/sda /boot/bootlx</i>
53 # <i>abootconf /dev/sda 2</i>
54 </pre>
55
56 <note>
57 If you use a different partitioning scheme than the one we use
58 throughout this chapter, you have to change the commands accordingly.
59 Please read the appropriate manual pages (<c>man 8 swriteboot</c> and
60 <c>man 8 abootconf</c>).
61 </note>
62
63 <p>
64 Additionally, you can make Gentoo boot more easily by setting up the
65 aboot configuration file and SRM boot_osflags variable. You will need to
66 make sure that the bootdef_dev is also properly set (easier to do at the
67 console than from Linux).
68 </p>
69
70 <pre caption = "Improve booting Gentoo">
71 # <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' &gt; /etc/aboot.conf</i>
72 # <i>echo -n 0 &gt; /proc/srm_environment/named_variables/boot_osflags</i>
73 # <i>echo -n '' &gt; /proc/srm_environment/named_variables/boot_file</i>
74 </pre>
75
76 <p>
77 If you're installing using a serial console, don't forget to include
78 the serial console boot flag in <path>aboot.conf</path>. See
79 <path>/etc/aboot.conf.example</path> for some further information.
80 </p>
81
82 <p>
83 Aboot is now configured and ready to use. Continue with <uri
84 link="#reboot">Rebooting the System</uri>.
85 </p>
86
87 </body>
88 </section>
89 <section id="milo">
90 <title>Alternative: Using MILO</title>
91 <body>
92
93 <p>
94 Before continuing, you should decide on how to use MILO. In this
95 section, we will assume that you want to make a MILO boot floppy. If you
96 are going to boot from an MS-DOS partition on your hard disk, you should
97 amend the commands appropriately.
98 </p>
99
100 <p>
101 To install MILO, we use <c>emerge</c>.
102 </p>
103
104 <pre caption = "Installing MILO">
105 # <i>emerge --usepkg milo</i>
106 </pre>
107
108 <p>
109 After MILO has been installed, the MILO images should be in
110 <path>/opt/milo</path>. The commands below make a bootfloppy for use
111 with MILO. Remember to use the correct image for your Alpha-system.
112 </p>
113
114 <pre caption = "Installing MILO on a floppy">
115 <comment>(First insert a blank floppy)</comment>
116 # <i>fdformat /dev/fd0</i>
117 # <i>mformat a:</i>
118 # <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
119 # <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
120 <comment>(Only if you have a Ruffian:</comment>
121 # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
122 <comment>)</comment>
123 # <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
124 </pre>
125
126 <p>
127 Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
128 set environment variables in your ARCS Firmware to get MILO to start;
129 this is all explained in the <uri
130 link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples
131 on common systems, and examples of the commands to use in interactive mode.
132 </p>
133
134 <p>
135 Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri>
136 is a <e>bad</e> idea.
137 </p>
138
139 <p>
140 Now continue with <uri link="#reboot">Rebooting the System</uri>.
141 </p>
142
143 </body>
144 </section>
145 <section id="reboot">
146 <title>Rebooting the System</title>
147 <subsection>
148 <body>
149
150 <p>
151 Exit the chrooted environment and unmount all mounted partitions. Then type in
152 that one magical command you have been waiting for: <c>reboot</c>.
153 </p>
154
155 <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
156 # <i>exit</i>
157 cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
158 cdimage ~# <i>reboot</i>
159 </pre>
160
161 <p>
162 Of course, don't forget to remove the bootable CD, otherwise the CD will be
163 booted again instead of your new Gentoo system.
164 </p>
165
166 <p>
167 Once rebooted in your Gentoo installation, finish up with <uri
168 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
169 </p>
170
171 </body>
172 </subsection>
173 </section>
174
175 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20