/[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.1 - (hide annotations) (download) (as text)
Fri Apr 2 08:14:45 2004 UTC (10 years, 5 months ago) by swift
Branch: MAIN
File MIME type: application/xml
#42823 - Separate architecture specific instructions in separate handbooks

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     <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6    
7     <!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-bootloader.xml,v 1.2 2004/03/30 13:35:22 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="?part=1&amp;chap=10">Installing Necessary System Tools</uri>.
85     </p>
86    
87     </body>
88     </section>
89     <section id="milo">
90     <title>Alternative: Using MILO</title>
91     <body>
92    
93     <impo>
94     MILO can only be used with alpha-based systems!
95     </impo>
96    
97     <p>
98     Before continuing, you should decide on how to use MILO. In this
99     section, we will assume that you want to make a MILO boot floppy. If you
100     are going to boot from an MS-DOS partition on your hard disk, you should
101     amend the commands appropriately.
102     </p>
103    
104     <p>
105     To install MILO, we use <c>emerge</c>.
106     </p>
107    
108     <pre caption = "Installing MILO">
109     # <i>emerge --usepkg milo</i>
110     </pre>
111    
112     <p>
113     After MILO has been installed, the MILO images should be in
114     <path>/opt/milo</path>. The commands below make a bootfloppy for use
115     with MILO. Remember to use the correct image for your Alpha-system.
116     </p>
117    
118     <pre caption = "Installing MILO on a floppy">
119     <comment>(First insert a blank floppy)</comment>
120     # <i>fdformat /dev/fd0</i>
121     # <i>mformat a:</i>
122     # <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i>
123     # <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i>
124     <comment>(Only if you have a Ruffian:</comment>
125     # <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i>
126     <comment>)</comment>
127     # <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i>
128     </pre>
129    
130     <p>
131     Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to
132     set environment variables in your ARCS Firmware to get MILO to start;
133     this is all explained in the <uri
134     link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples
135     on common systems, and examples of the commands to use in interactive mode.
136     </p>
137    
138     <p>
139     Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri>
140     is a <e>bad</e> idea.
141     </p>
142    
143     <p>
144     Now continue with <uri link="?part=1&amp;chap=10">Installing Necessary System
145     Tools</uri>.
146     </p>
147    
148     </body>
149     </section>
150     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20