| 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 |
swift |
1.13 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-sparc-bootloader.xml,v 1.12 2005/01/21 09:00:23 swift Exp $ -->
|
| 8 |
swift |
1.1 |
|
| 9 |
|
|
<sections>
|
| 10 |
swift |
1.8 |
|
| 11 |
swift |
1.13 |
<version>2.00</version>
|
| 12 |
|
|
<date>2005-03-28</date>
|
| 13 |
swift |
1.8 |
|
| 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 |
|
|
</body>
|
| 28 |
|
|
</subsection>
|
| 29 |
|
|
</section>
|
| 30 |
|
|
<section>
|
| 31 |
|
|
<title>Installing the SPARC Bootloader: SILO</title>
|
| 32 |
|
|
<body>
|
| 33 |
|
|
|
| 34 |
|
|
<p>
|
| 35 |
|
|
It is now time to install and configure <uri
|
| 36 |
|
|
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot
|
| 37 |
|
|
LOader.
|
| 38 |
|
|
</p>
|
| 39 |
|
|
|
| 40 |
|
|
<pre caption = "Installing SILO">
|
| 41 |
swift |
1.13 |
# <i>emerge silo</i>
|
| 42 |
swift |
1.1 |
</pre>
|
| 43 |
|
|
|
| 44 |
|
|
<p>
|
| 45 |
|
|
Now open up your favorite editor (we use <c>nano</c> as an example) and
|
| 46 |
|
|
create <path>/etc/silo.conf</path>.
|
| 47 |
|
|
</p>
|
| 48 |
|
|
|
| 49 |
|
|
<pre caption = "Creating /etc/silo.conf">
|
| 50 |
|
|
# <i>nano -w /etc/silo.conf</i>
|
| 51 |
|
|
</pre>
|
| 52 |
|
|
|
| 53 |
|
|
<p>
|
| 54 |
neysx |
1.6 |
Below you'll find an example <path>silo.conf</path> file. It uses the
|
| 55 |
swift |
1.1 |
partitioning scheme we use throughout this book and
|
| 56 |
swift |
1.13 |
<path>kernel-2.4.29</path> as kernelimage.
|
| 57 |
swift |
1.1 |
</p>
|
| 58 |
|
|
|
| 59 |
|
|
<pre caption = "Example /etc/silo.conf">
|
| 60 |
swift |
1.12 |
partition = 1 <comment># Boot partition (= root partition)</comment>
|
| 61 |
|
|
root = /dev/sda1 <comment># Root partition</comment>
|
| 62 |
swift |
1.2 |
timeout = 150 <comment># Wait 15 seconds before booting the default section</comment>
|
| 63 |
swift |
1.1 |
|
| 64 |
swift |
1.13 |
image = /boot/kernel-2.4.29
|
| 65 |
swift |
1.1 |
label = linux
|
| 66 |
|
|
</pre>
|
| 67 |
|
|
|
| 68 |
|
|
<p>
|
| 69 |
|
|
If you use the example <path>silo.conf</path> delivered by Portage, be
|
| 70 |
|
|
sure to comment out <e>all</e> lines that you do not need.
|
| 71 |
|
|
</p>
|
| 72 |
|
|
|
| 73 |
|
|
<p>
|
| 74 |
swift |
1.3 |
If the physical disk on which you want to install SILO (as bootloader) differs
|
| 75 |
|
|
from the physical disk on which <path>/etc/silo.conf</path> resides, you must
|
| 76 |
|
|
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that
|
| 77 |
|
|
<path>/boot</path> is a separate partition on that disk, copy over the
|
| 78 |
swift |
1.1 |
configuration file to <path>/boot</path> and run <c>/sbin/silo</c>:
|
| 79 |
|
|
</p>
|
| 80 |
|
|
|
| 81 |
swift |
1.3 |
<pre caption = "Only if /boot and the SILO destination are on the same disk">
|
| 82 |
swift |
1.1 |
# <i>cp /etc/silo.conf /boot</i>
|
| 83 |
|
|
# <i>/sbin/silo -C /boot/silo.conf</i>
|
| 84 |
|
|
/boot/silo.conf appears to be valid
|
| 85 |
|
|
</pre>
|
| 86 |
|
|
|
| 87 |
|
|
<p>
|
| 88 |
swift |
1.3 |
Otherwise just run <c>/sbin/silo</c>:
|
| 89 |
swift |
1.1 |
</p>
|
| 90 |
|
|
|
| 91 |
|
|
<pre caption = "Run silo">
|
| 92 |
|
|
# <i>/sbin/silo</i>
|
| 93 |
|
|
/etc/silo.conf appears to be valid
|
| 94 |
|
|
</pre>
|
| 95 |
|
|
|
| 96 |
|
|
<p>
|
| 97 |
swift |
1.4 |
Now continue with <uri link="#reboot">Rebooting the System</uri>.
|
| 98 |
swift |
1.1 |
</p>
|
| 99 |
|
|
|
| 100 |
|
|
</body>
|
| 101 |
|
|
</section>
|
| 102 |
cam |
1.5 |
<section id="reboot">
|
| 103 |
swift |
1.4 |
<title>Rebooting the System</title>
|
| 104 |
|
|
<subsection>
|
| 105 |
|
|
<body>
|
| 106 |
|
|
|
| 107 |
|
|
<p>
|
| 108 |
|
|
Exit the chrooted environment and unmount all mounted partitions. Then type in
|
| 109 |
|
|
that one magical command you have been waiting for: <c>reboot</c>.
|
| 110 |
|
|
</p>
|
| 111 |
|
|
|
| 112 |
|
|
<pre caption="Exiting the chroot, unmounting all partitions and rebooting">
|
| 113 |
|
|
# <i>exit</i>
|
| 114 |
swift |
1.7 |
cdimage ~# <i>cd</i>
|
| 115 |
swift |
1.4 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/proc /mnt/gentoo</i>
|
| 116 |
|
|
cdimage ~# <i>reboot</i>
|
| 117 |
|
|
</pre>
|
| 118 |
|
|
|
| 119 |
|
|
<p>
|
| 120 |
|
|
Of course, don't forget to remove the bootable CD, otherwise the CD will be
|
| 121 |
|
|
booted again instead of your new Gentoo system.
|
| 122 |
|
|
</p>
|
| 123 |
|
|
|
| 124 |
|
|
<p>
|
| 125 |
|
|
Once rebooted in your Gentoo installation, finish up with <uri
|
| 126 |
|
|
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>.
|
| 127 |
|
|
</p>
|
| 128 |
|
|
|
| 129 |
|
|
</body>
|
| 130 |
|
|
</subsection>
|
| 131 |
|
|
</section>
|
| 132 |
swift |
1.1 |
</sections>
|
Parent Directory
| 
Revision Log