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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.48 - (hide annotations) (download) (as text)
Wed Mar 16 07:45:13 2011 UTC (3 years, 8 months ago) by nightmorph
Branch: MAIN
Changes since 1.47: +5 -6 lines
File MIME type: application/xml
use different bind mount, bug 253681

1 swift 1.1 <?xml version='1.0' encoding='UTF-8'?>
2     <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 nightmorph 1.48 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-bootloader.xml,v 1.47 2010/07/21 01:28:29 nightmorph Exp $ -->
4 swift 1.1
5     <!-- The content of this document is licensed under the CC-BY-SA license -->
6 neysx 1.34 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
7 swift 1.1
8     <sections>
9 swift 1.14
10 nightmorph 1.47 <abstract>
11     Several bootloaders exist. Each one of them has its own way of
12     configuration. In this chapter we'll describe all possibilities for you
13     and step you through the process of configuring a bootloader to your
14     needs.
15     </abstract>
16    
17 nightmorph 1.48 <version>10.2</version>
18     <date>2011-03-16</date>
19 swift 1.14
20 swift 1.1 <section>
21 nightmorph 1.46 <title>Making your Choice</title>
22 swift 1.1 <subsection>
23     <title>Introduction</title>
24     <body>
25    
26     <p>
27 nightmorph 1.46 Now that your kernel is configured and compiled and the necessary system
28     configuration files are filled in correctly, it is time to install a
29     program that will fire up your kernel when you start the system. Such a
30     program is called a <e>bootloader</e>.
31     </p>
32    
33     <p>
34     The bootloader that you use will depend upon the type of PPC machine you have.
35 swift 1.1 </p>
36    
37     <p>
38 swift 1.28 If you are using a NewWorld Apple or IBM machine, you need to use
39     <uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options,
40     <uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>.
41     The Pegasos does not require a bootloader, but you will need to emerge
42 nightmorph 1.41 <uri link="#bootcreator">bootcreator</uri> to create SmartFirmware boot menus.
43 swift 1.1 </p>
44    
45     </body>
46     </subsection>
47     </section>
48 neysx 1.2 <section id="yaboot">
49 swift 1.21 <title>Default: Using yaboot</title>
50 swift 1.1 <subsection>
51     <title>Introduction</title>
52     <body>
53    
54     <impo>
55 nightmorph 1.37 yaboot can only be used on NewWorld Apple and IBM systems!
56 swift 1.1 </impo>
57 nightmorph 1.37
58 sejo 1.17 <p>
59 fox2mike 1.33 In order to find the boot devices, yaboot needs access to the device nodes
60     created by udev on startup and the sysfs filesystem. These two filesystems
61     are found at <path>/dev</path> and <path>sys</path> respectively. To do this,
62     you will need to "bind mount" these filesystems from the Installation CD's root
63     to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot.
64     If you have already bind mounted these filesystems, there is no need to do it
65     again.
66 sejo 1.17 </p>
67 nightmorph 1.37
68 fox2mike 1.33 <pre caption="Bind-mounting the device and sysfs filesystems">
69 sejo 1.17 # <i>exit </i> # this will exit the chroot
70 nightmorph 1.48 # <i>mount --rbind /dev /mnt/gentoo/dev</i>
71     # <i>mount --rbind /sys /mnt/gentoo/sys</i>
72 sejo 1.17 # <i>chroot /mnt/gentoo /bin/bash</i>
73     # <i>/usr/sbin/env-update &amp;&amp; source /etc/profile </i>
74     </pre>
75 swift 1.21
76 swift 1.1 <p>
77 swift 1.28 To set up yaboot, you can use <c>yabootconfig</c> to automatically create a
78     configuration file for you. If you are installing Gentoo on a G5 (where
79 nightmorph 1.46 <c>yabootconfig</c> does not always work), or you plan to boot from FireWire
80 swift 1.28 or USB, you will need to manually configure yaboot.
81 swift 1.1 </p>
82    
83 josejx 1.25 <note>
84 nightmorph 1.46 You will need to manually edit the <path>yaboot.conf</path> when using
85     <c>genkernel</c>, even if <c>yabootconfig</c> is used. The kernel image section
86     of <path>yaboot.conf</path> should be modified as follows (using
87     <path>vmlinux</path> and <path>initrd</path> as the name of kernel and
88     <path>initrd</path> image):
89 josejx 1.25 </note>
90    
91 swift 1.28 <pre caption="Adding genkernel boot arguments to yaboot.conf">
92     <comment>###########################################################
93     ## This section can be duplicated if you have more than one
94 nightmorph 1.41 ## kernel or set of boot options - replace the image and initrd
95     ## with the exact filename of your kernel and initrd image.
96 swift 1.28 ###########################################################</comment>
97 nightmorph 1.46 image=/boot/<keyval id="genkernel-name"/>
98 josejx 1.25 label=Linux
99 rane 1.35 root=/dev/ram0
100 josejx 1.25 partition=3
101 nightmorph 1.46 initrd=/boot/<keyval id="genkernel-initrd"/>
102 nightmorph 1.37 <comment># You can add additional kernel arguments to append such as
103 swift 1.28 # rootdelay=10 for a USB/Firewire Boot</comment>
104 nightmorph 1.45 append="real_root=/dev/sda3 init=/linuxrc"
105 josejx 1.25 read-only
106 swift 1.28 <comment>##########################################################</comment>
107 josejx 1.25 </pre>
108    
109 swift 1.1 <ul>
110     <li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li>
111     <li>
112 swift 1.21 <uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri>
113 swift 1.1 </li>
114     </ul>
115    
116     </body>
117     </subsection>
118     <subsection id="yabootconfig">
119     <title>Default: Using yabootconfig</title>
120     <body>
121    
122     <p>
123     <c>yabootconfig</c> will auto-detect the partitions on your machine and will
124 swift 1.13 set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X.
125 swift 1.1 </p>
126 nightmorph 1.37
127 swift 1.1 <p>
128 swift 1.21 To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition,
129 fox2mike 1.33 and <path>/etc/fstab</path> must be configured to reflect your Linux
130 nightmorph 1.41 partitions (note that the Bootstrap partition should <e>not</e> be in your
131     fstab). These steps should have already been completed before, but check
132     <path>/etc/fstab</path> before proceeding. Now, install <c>yaboot</c>.
133 swift 1.1 </p>
134 nightmorph 1.37
135 josejx 1.38 <pre caption = "Installing yaboot">
136 fox2mike 1.33 # <i>emerge yaboot</i>
137 swift 1.1 </pre>
138 nightmorph 1.37
139 swift 1.1 <p>
140 nightmorph 1.46 Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First, the
141     program will confirm the location of the bootstrap partition. If you are using
142     the suggested disk partitioning scheme, your bootstrap partition should be
143     <path>/dev/sda2</path>. Type <c>Y</c> if the output is correct. If not, double
144     check your <path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your
145     system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
146     you. <c>mkofboot</c> is used to format the Apple_Bootstrap partition, and
147     install the yaboot configuration file into it. After this enter the chroot
148     again.
149 swift 1.1 </p>
150 swift 1.28
151     <pre caption="Re-enter the chroot">
152 sejo 1.10 # <i>chroot /mnt/gentoo /bin/bash</i>
153 sejo 1.11 # <i>/usr/sbin/env-update &amp;&amp; source /etc/profile</i>
154 sejo 1.10 </pre>
155 swift 1.1
156     <p>
157 nightmorph 1.41 You should verify the contents of <path>/etc/yaboot.conf</path>. If you make
158     changes to <path>/etc/yaboot.conf</path> (like setting the default/boot OS),
159     make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap
160     partition. Whenever you make a change to yaboot.conf, like when testing a new
161     kernel, always remember to run <c>ybin -v</c> to update the bootstrap
162 swift 1.15 partition.
163 swift 1.1 </p>
164    
165     <p>
166 swift 1.7 Now continue with <uri link="#reboot">Rebooting the System</uri>.
167 swift 1.1 </p>
168    
169     </body>
170     </subsection>
171     <subsection id="manual_yaboot">
172 swift 1.21 <title>Alternative: Manual yaboot Configuration</title>
173 swift 1.1 <body>
174    
175     <p>
176 nightmorph 1.41 First, install <c>yaboot</c> on your system:
177 swift 1.1 </p>
178    
179 nightmorph 1.41 <pre caption="Installing yaboot">
180     # <i>emerge yaboot</i>
181 swift 1.1 </pre>
182    
183     <p>
184 swift 1.28 An example <path>yaboot.conf</path> file is given below, but you will need to
185 nightmorph 1.45 alter it to fit your needs.
186 swift 1.1 </p>
187    
188     <pre caption = "/etc/yaboot.conf">
189     <comment>## /etc/yaboot.conf
190     ##
191     ## run: "man yaboot.conf" for details. Do not make changes until you have!!
192     ## see also: /usr/share/doc/yaboot/examples for example configurations.
193     ##
194     ## For a dual-boot menu, add one or more of:
195 nightmorph 1.45 ## bsd=/dev/sdaX, macos=/dev/sdaY, macosx=/dev/sdaZ
196 swift 1.1
197 nightmorph 1.37 ## The bootstrap partition:</comment>
198 swift 1.1
199 nightmorph 1.45 boot=/dev/sda2
200 swift 1.1
201 nightmorph 1.43 <comment>## ofboot is the Open Firmware way to specify the bootstrap partition.
202 swift 1.18 ## If this isn't defined, yaboot fails on the G5 and some G4s (unless
203     ## you pass the necessary arguments to the mkofboot/ybin program).
204 nightmorph 1.45 ## hd:X means /dev/sdaX.
205 swift 1.1 ##
206     ## G5 users should uncomment this line!!
207 nightmorph 1.37
208 swift 1.28 #ofboot=hd:2
209 swift 1.1
210 swift 1.28 ## Users booting from firewire should use something like this line:
211     # ofboot=fw/node/sbp-2/disk@0:
212    
213     ## Users booting from USB should use something like this line:
214     # ofboot=usb/disk@0:
215 swift 1.1
216 nightmorph 1.43 ## hd: is shorthand for the first hard drive Open Firmware sees</comment>
217 swift 1.1 device=hd:
218    
219 swift 1.28 <comment>## Firewire and USB users will need to specify the whole OF device name
220     ## This can be found using ofpath, which is included with yaboot.
221    
222     # device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0:
223     </comment>
224    
225 swift 1.1 delay=5
226     defaultos=macosx
227     timeout=30
228     install=/usr/lib/yaboot/yaboot
229     magicboot=/usr/lib/yaboot/ofboot
230    
231 nightmorph 1.41 <comment>############################################################
232     ## This section can be duplicated if you have more than one
233     ## kernel or set of boot options - replace the image variable
234     ## with the exact filename of your kernel.
235     ###########################################################</comment>
236     image=/boot/<keyval id="kernel-name"/>
237 swift 1.1 label=Linux
238 nightmorph 1.45 root=/dev/sda3
239 swift 1.18 partition=3
240 swift 1.28 <comment># append="rootdelay=10" # Required for booting USB/Firewire</comment>
241 swift 1.1 read-only
242 swift 1.18 <comment>##################
243 swift 1.1
244 swift 1.18 ## G5 users and some G4 users should set
245 nightmorph 1.41 ## macos=hd:13/
246 swift 1.1 ## macosx=hd:12
247     ## instead of the example values.</comment>
248 nightmorph 1.45 macos=/dev/sda13
249     macosx=/dev/sda12
250 swift 1.1 enablecdboot
251     enableofboot
252     </pre>
253    
254     <p>
255 swift 1.28 Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format
256     the Apple_bootstrap partition and install the settings. If you change
257     yaboot.conf after the Apple_bootstrap partition has been created, you can
258     update the settings by running <c>ybin -v</c>
259 swift 1.1 </p>
260    
261 josejx 1.39 <pre caption="Setting up the bootstrap partition">
262 nightmorph 1.40 # <i>mkofboot -v</i>
263 josejx 1.39 </pre>
264    
265 swift 1.1 <p>
266 swift 1.21 For more information on yaboot, take a look at the <uri
267 swift 1.15 link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For
268 swift 1.7 now, continue the installation with <uri link="#reboot">Rebooting the
269     System</uri>.
270 swift 1.1 </p>
271    
272     </body>
273     </subsection>
274     </section>
275     <section id="bootx">
276     <title>Alternative: BootX</title>
277     <body>
278    
279     <impo>
280 josejx 1.36 BootX can only be used on OldWorld Apple systems with MacOS 9 or earlier!
281 swift 1.1 </impo>
282    
283     <p>
284 josejx 1.25 Since BootX boots Linux from within MacOS, the kernel will need to be copied
285     from the Linux Partition to the MacOS partition. First, mount the MacOS
286     partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the
287     MacOS partition number, sda6 is used as an example here. Once the partition is
288     mounted, we'll copy the kernel to the system folder so BootX can find it.
289 swift 1.1 </p>
290    
291 josejx 1.25 <pre caption="Copying the kernel to the MacOS partition">
292 josejx 1.22 # <i>exit</i>
293     cdimage ~# <i>mkdir /mnt/mac</i>
294     cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
295 nightmorph 1.41 cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels/<keyval id="kernel-name"/>"</i>
296 josejx 1.22 </pre>
297    
298 swift 1.1 <p>
299 swift 1.28 If genkernel is used, both the kernel and initrd will need to be copied to the
300     MacOS partition.
301 josejx 1.25 </p>
302    
303     <pre caption="Copying the Genkernel kernel and initrd to the MacOS partition">
304     # <i>exit</i>
305     cdimage ~# <i>mkdir /mnt/mac</i>
306     cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i>
307 nightmorph 1.46 cdimage ~# <i>cp /mnt/gentoo/boot/<keyval id="genkernel-name"/> "/mnt/mac/System Folder/Linux Kernels"</i>
308     cdimage ~# <i>cp /mnt/gentoo/boot/<keyval id="genkernel-initrd"/> "/mnt/mac/System Folder"</i>
309 josejx 1.25 </pre>
310    
311     <p>
312 swift 1.28 Now that the kernel is copied over, we'll need to reboot to set up BootX.
313 dertobi123 1.5 </p>
314    
315 josejx 1.22 <pre caption="Unmounting all partitions and rebooting">
316     cdimage ~# <i>cd /</i>
317 nightmorph 1.37 cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo /mnt/mac</i>
318 swift 1.7 cdimage ~# <i>reboot</i>
319     </pre>
320    
321     <p>
322 nightmorph 1.37 Of course, don't forget to remove the bootable CD, otherwise the CD will be
323     booted again instead of MacOS.
324 swift 1.7 </p>
325    
326     <p>
327 swift 1.28 Once the machine has booted into MacOS, open the BootX control panel. If you're
328 neysx 1.30 not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM
329 swift 1.28 disk</c>. If you are using genkernel, ensure that the genkernel initrd is
330     selected instead of the Installation CD initrd. If not using genkernel,
331     there is now an option to specify the machine's Linux root disk and partition.
332     Fill these in with the appropriate values. Depending upon the kernel
333     configuration, additional boot arguments may need to be applied.
334 swift 1.7 </p>
335    
336     <p>
337 nightmorph 1.37 BootX can be configured to start Linux upon boot. If you do this, you will first
338     see your machine boot into MacOS then, during startup, BootX will load and start
339     Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home
340     page</uri> for more information.
341 swift 1.7 </p>
342    
343 fox2mike 1.33 <impo>
344     Make sure that you have support for HFS and HFS+ filesystems in your kernel,
345     otherwise you will not be able to upgrade or change the kernel on your MacOS
346     partition.
347     </impo>
348    
349 swift 1.7 <p>
350 swift 1.15 Now reboot again and boot into Linux, then continue with <uri
351 swift 1.7 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
352     </p>
353    
354     </body>
355     </section>
356 swift 1.28 <section id="quik">
357     <title>Alternative: quik</title>
358     <body>
359    
360     <p>
361 nightmorph 1.46 <c>quik</c> allows OldWorld Macs to boot without MacOS. However, it isn't well
362     supported and has a number of quirks. If you have the option, it is recommended
363 swift 1.28 that you use BootX instead since it is much more reliable and easier to set up
364     than quik.
365     </p>
366    
367     <p>
368 nightmorph 1.46 First, we'll need to install <c>quik</c>:
369 swift 1.28 </p>
370    
371     <pre caption="Emerge quik">
372     # <i>emerge quik</i>
373     </pre>
374    
375     <p>
376 nightmorph 1.41 Next, we'll need to set it up. Edit <path>/etc/quik.conf</path> and set your
377     image to the kernel that we copied to your boot partition.
378 swift 1.28 </p>
379    
380     <pre caption="Configuring quik.conf">
381     # Example of quik.conf
382 nightmorph 1.46 init-message = "Gentoo Linux\n"
383 nightmorph 1.41 <comment># This is the boot partition</comment>
384     partition = 2
385 nightmorph 1.45 root = /dev/sda4
386 swift 1.28 timeout = 30
387     default = gentoo
388 nightmorph 1.41 <comment># This is your kernel</comment>
389     image = /<keyval id="kernel-name"/>
390     label = gentoo
391 swift 1.28 </pre>
392    
393     <p>
394 nightmorph 1.46 Your <path>quik.conf</path> file <e>must</e> be on the same disk as the quik
395     boot images, however it can be on a different partition on the same disk,
396     although it is recommended to move it to your boot partition.
397 swift 1.28 </p>
398    
399     <pre caption="Moving quik.conf to /boot">
400     # <i>mv /etc/quik.conf /boot/quik.conf</i>
401     </pre>
402    
403     <p>
404     We will now set your boot variables so that quik loads on boot. To do this,
405     we'll use a program called <c>nvsetenv</c>. The variables that you want to
406     set vary from machine to machine, it's best to find your machine's
407     <uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri>
408     before attempting this.
409     </p>
410    
411     <pre caption="Setting the boot variables">
412     # <i>nvsetenv auto-boot true</i> <comment># Set to false if you want to boot into OF, not all models can display the OF output</comment>
413     # <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment>
414     # <i>nvsetenv input-device kbd</i>
415     # <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment>
416     # <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment>
417 nightmorph 1.45 # <i>nvsetenv boot-file /boot/<keyval id="kernel-name"/> root=/dev/sda4</i> <comment>First item is the path to the kernel, the second is the root partition. You may append any kernel options to the end of this line.</comment>
418 swift 1.28 # <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment>
419     </pre>
420    
421     <note>
422 nightmorph 1.41 It is also possible to change your boot variables from MacOS. Depending upon
423     the model, either <uri
424     link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or
425     <uri
426     link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin">
427     Apple System Disk</uri> should be used. Please see the quik quirks page above
428     for more information.
429 swift 1.28 </note>
430    
431     <p>
432     Now that we've set up our machine to boot, we'll need to make sure the boot
433     images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It
434     should tell you that it has installed the first stage QUIK boot block.
435     </p>
436    
437     <note>
438     If something has gone wrong, you can always reset your PRAM back to the default
439     values by holding down <c>command + option + p + r</c> before powering on your
440     machine. This will clear the values you set with nvsetenv and should allow you
441     to boot either a MacOS bootdisk or a Linux bootdisk.
442     </note>
443    
444     <p>
445     Now, continue the installation with
446     <uri link="#reboot">Rebooting the System</uri>.
447     </p>
448    
449     </body>
450     </section>
451 swift 1.21 <section id="bootcreator">
452     <title>Alternative: BootCreator</title>
453     <body>
454    
455     <impo>
456 nightmorph 1.37 BootCreator will build a nice SmartFirmware bootmenu written in Forth for the
457 swift 1.21 Pegasos.
458     </impo>
459    
460     <p>
461 nightmorph 1.37 First make sure you have <c>bootcreator</c> installed on your system:
462 swift 1.21 </p>
463    
464     <pre caption = "Installing bootcreator">
465 nightmorph 1.41 # <i>emerge bootcreator</i>
466 swift 1.21 </pre>
467    
468     <p>
469     Now copy the file <path>/etc/bootmenu.example</path> into
470 swift 1.28 <path>/etc/bootmenu</path> and edit it to suit your needs:
471 swift 1.21 </p>
472    
473     <pre caption = "Edit the bootcreator config file">
474     # <i>cp /etc/bootmenu.example /etc/bootmenu</i>
475     # <i>nano -w /etc/bootmenu</i>
476     </pre>
477    
478     <p>
479 nightmorph 1.41 Below is a complete <path>/etc/bootmenu</path> config file. vmlinux and
480     initrd should be replaced by your kernel and initrd image names.
481 swift 1.21 </p>
482    
483     <pre caption = "bootcreator config file">
484     <comment>#
485     # Example description file for bootcreator 1.1
486     #</comment>
487    
488     [VERSION]
489     1
490    
491     [TITLE]
492     Boot Menu
493    
494     [SETTINGS]
495     AbortOnKey = false
496     Timeout = 9
497     Default = 1
498    
499     [SECTION]
500     Local HD -> Morphos (Normal)
501     ide:0 boot2.img ramdebug edebugflags="logkprintf"
502    
503     [SECTION]
504 nightmorph 1.37 Local HD -> Linux (Normal)
505 nightmorph 1.45 ide:0 <keyval id="kernel-name"/> video=radeonfb:1024x768@70 root=/dev/sda3
506 swift 1.21
507 swift 1.28 [SECTION]
508     Local HD -> Genkernel (Normal)
509 nightmorph 1.46 ide:0 <keyval id="genkernel-name"/> root=/dev/ram0
510     real_root=/dev/sda3 init=/linuxrc initrd=<keyval id="genkernel-initrd"/>
511 swift 1.21 </pre>
512    
513     <p>
514 nightmorph 1.41 Finally the <path>bootmenu</path> must be transferred into Forth and copied to
515 nightmorph 1.37 your boot partition, so that the SmartFirmware can read it. Therefore you have
516     to call <c>bootcreator</c>:
517 swift 1.21 </p>
518    
519     <pre caption = "Install the bootmenu">
520     # <i>bootcreator /etc/bootmenu /boot/menu</i>
521     </pre>
522    
523     <note>
524 nightmorph 1.37 Be sure to have a look into the SmartFirmware's settings when you reboot, that
525 swift 1.21 <path>menu</path> is the file that will be loaded by default.
526     </note>
527    
528     <p>
529 nightmorph 1.37 For now, continue the installation with <uri link="#reboot">Rebooting the
530     System</uri>.
531 swift 1.21 </p>
532    
533     </body>
534     </section>
535 cam 1.8 <section id="reboot">
536 swift 1.7 <title>Rebooting the System</title>
537     <subsection>
538     <body>
539    
540     <p>
541 nightmorph 1.37 Exit the chrooted environment and unmount all mounted partitions. Then type in
542     that one magical command you have been waiting for: <c>reboot</c>.
543 swift 1.7 </p>
544    
545     <pre caption="Exiting the chroot, unmounting all partitions and rebooting">
546     # <i>exit</i>
547 nightmorph 1.37 livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo</i>
548 swift 1.19 livecd ~# <i>reboot</i>
549 swift 1.7 </pre>
550    
551 dertobi123 1.5 <p>
552 nightmorph 1.37 Once rebooted in your Gentoo installation, finish up with <uri
553 swift 1.7 link="?part=1&amp;chap=11">Finalizing your Gentoo Installation</uri>.
554 swift 1.1 </p>
555    
556     </body>
557 swift 1.7 </subsection>
558 swift 1.1 </section>
559     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20