1 |
nightmorph 07/04/01 23:16:30 |
2 |
|
3 |
Modified: hb-install-ppc64-bootloader.xml |
4 |
hb-install-ppc64-disk.xml |
5 |
hb-install-ppc64-kernel.xml |
6 |
hb-install-ppc64-medium.xml |
7 |
Log: |
8 |
ppc64 done |
9 |
|
10 |
Revision Changes Path |
11 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml |
12 |
|
13 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?rev=1.15&view=markup |
14 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?rev=1.15&content-type=text/plain |
15 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?r1=1.14&r2=1.15 |
16 |
|
17 |
Index: hb-install-ppc64-bootloader.xml |
18 |
=================================================================== |
19 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml,v |
20 |
retrieving revision 1.14 |
21 |
retrieving revision 1.15 |
22 |
diff -u -r1.14 -r1.15 |
23 |
--- hb-install-ppc64-bootloader.xml 14 Mar 2007 06:24:40 -0000 1.14 |
24 |
+++ hb-install-ppc64-bootloader.xml 1 Apr 2007 23:16:30 -0000 1.15 |
25 |
@@ -4,11 +4,11 @@ |
26 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
27 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
28 |
|
29 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml,v 1.14 2007/03/14 06:24:40 nightmorph Exp $ --> |
30 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml,v 1.15 2007/04/01 23:16:30 nightmorph Exp $ --> |
31 |
|
32 |
<sections> |
33 |
|
34 |
-<version>7.0</version> |
35 |
+<version>8.0</version> |
36 |
<date>2006-08-30</date> |
37 |
|
38 |
<section> |
39 |
@@ -45,13 +45,12 @@ |
40 |
</impo> |
41 |
|
42 |
<p> |
43 |
-There are two ways to configure yaBoot for your system. You can use the |
44 |
-new and improved <c>yabootconfig</c> included with |
45 |
-<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If |
46 |
-for some reason you do not want to run <c>yabootconfig</c> to |
47 |
-automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
48 |
-on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
49 |
-the sample file already installed on your system. |
50 |
+There are two ways to configure yaBoot for your system. You can use the new and |
51 |
+improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and |
52 |
+later to automatically set up yaboot. If for some reason you do not want to run |
53 |
+<c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or you |
54 |
+are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always |
55 |
+work), you can just edit the sample file already installed on your system. |
56 |
</p> |
57 |
|
58 |
<impo> |
59 |
@@ -102,19 +101,19 @@ |
60 |
</pre> |
61 |
|
62 |
<p> |
63 |
-Now run <c>yabootconfig</c>. The program will run and it will confirm |
64 |
-the location of the bootstrap partition. Type <c>Y</c> if it is correct. If |
65 |
-not, double check <path>/etc/fstab</path>. yabootconfig will then scan your |
66 |
-system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for |
67 |
-you. <c>mkofboot</c> is used to format the bootstrap partition, and install |
68 |
-the yaboot configuration file into it. |
69 |
+Now run <c>yabootconfig</c>. The program will run and it will confirm the |
70 |
+location of the bootstrap partition. Type <c>Y</c> if it is correct. If not, |
71 |
+double check <path>/etc/fstab</path>. yabootconfig will then scan your system |
72 |
+setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. |
73 |
+<c>mkofboot</c> is used to format the bootstrap partition, and install the |
74 |
+yaboot configuration file into it. |
75 |
</p> |
76 |
|
77 |
<p> |
78 |
-You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
79 |
-you make changes to <path>/etc/yaboot.conf</path> (like setting the |
80 |
-default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
81 |
-bootstrap partition. |
82 |
+You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you |
83 |
+make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot |
84 |
+OS), make sure to rerun <c>ybin -v</c> to apply changes to the bootstrap |
85 |
+partition. |
86 |
</p> |
87 |
|
88 |
<p> |
89 |
@@ -176,9 +175,9 @@ |
90 |
|
91 |
<comment>################# |
92 |
## This section can be duplicated if you have more than one kernel or set of |
93 |
-## boot options - replace 2.6.17-gentoo-r5 with your kernel-version |
94 |
+## boot options - replace <keyval id="kernel-name"/> with your kernel-version |
95 |
#################</comment> |
96 |
-image=/boot/kernel-2.6.17-gentoo-r5 |
97 |
+image=/boot/<keyval id="kernel-name"/> |
98 |
label=Linux |
99 |
root=/dev/hda3 |
100 |
partition=3 |
101 |
@@ -191,25 +190,22 @@ |
102 |
</pre> |
103 |
|
104 |
<p> |
105 |
-Once <path>yaboot.conf</path> is set up the way you want it, you run |
106 |
-<c>mkofboot -v</c> to install the settings in the bootstrap partition. |
107 |
-<e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new |
108 |
-filesystem. |
109 |
+Once <path>yaboot.conf</path> is set up the way you want it, you run <c>mkofboot |
110 |
+-v</c> to install the settings in the bootstrap partition. <e>Don't forget |
111 |
+this!</e> Confirm when <c>mkofboot</c> asks you to create a new filesystem. |
112 |
</p> |
113 |
|
114 |
<p> |
115 |
-If all goes well, and you have the same |
116 |
-options as the sample above, your next reboot will give you a simple, |
117 |
-five-entry boot menu. If you update your yaboot config later on, you'll |
118 |
-just need to run <c>ybin -v</c> to update the bootstrap partition - |
119 |
-<c>mkofboot</c> is for initial setup only. |
120 |
+If all goes well, and you have the same options as the sample above, your next |
121 |
+reboot will give you a simple, five-entry boot menu. If you update your yaboot |
122 |
+config later on, you'll just need to run <c>ybin -v</c> to update the bootstrap |
123 |
+partition - <c>mkofboot</c> is for initial setup only. |
124 |
</p> |
125 |
|
126 |
<p> |
127 |
For more information on yaboot, take a look at the <uri |
128 |
-link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For |
129 |
-now, continue the installation with <uri link="#reboot">Rebooting your |
130 |
-System</uri>. |
131 |
+link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For now, |
132 |
+continue the installation with <uri link="#reboot">Rebooting your System</uri>. |
133 |
</p> |
134 |
|
135 |
</body> |
136 |
@@ -226,16 +222,22 @@ |
137 |
|
138 |
<ul> |
139 |
<li>Install yaboot-static</li> |
140 |
- <li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX |
141 |
- with your disk and partition for the PReP partition; this was in our |
142 |
- example /dev/sda1)</li> |
143 |
- <li>Next construct your own yaboot.conf file and place into /etc. |
144 |
- (Take a look at the config above, look into the man page of |
145 |
- yaboot.conf or look at the below yaboot.conf example)</li> |
146 |
- <li>Assuming your boot device in OF is pointing to the harddrive you |
147 |
- prep boot partition is on then it'll just work, otherwise at IPL time, |
148 |
- go into the multiboot menu and set the boot device to the one with |
149 |
- your prep boot partition.</li> |
150 |
+ <li> |
151 |
+ Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with |
152 |
+ your disk and partition for the PReP partition; this was in our example |
153 |
+ <path>/dev/sda1</path>) |
154 |
+ </li> |
155 |
+ <li> |
156 |
+ Next construct your own <path>yaboot.conf</path> file and place into |
157 |
+ <path>/etc</path>. (Take a look at the config above, look into the man page |
158 |
+ of yaboot.conf or look at the below <path>yaboot.conf</path> example.) |
159 |
+ </li> |
160 |
+ <li> |
161 |
+ Assuming your boot device in OF is pointing to the harddrive you prep boot |
162 |
+ partition is on then it'll just work, otherwise at IPL time, go into the |
163 |
+ multiboot menu and set the boot device to the one with your prep boot |
164 |
+ partition |
165 |
+ </li> |
166 |
<li>That's it!</li> |
167 |
</ul> |
168 |
|
169 |
@@ -246,22 +248,23 @@ |
170 |
default=linux |
171 |
timeout=50 |
172 |
|
173 |
-image=/boot/kernel-2.6.17-gentoo-r5 |
174 |
+image=/boot/<keyval id="kernel-name"/> |
175 |
label=linux |
176 |
append="console=ttyS0,9600" |
177 |
read-only |
178 |
</pre> |
179 |
|
180 |
<p> |
181 |
-For POWER4, POWER5, and blade-based hardware where the PReP disk partition |
182 |
-and the disk partition that contains your kernel are on the same physical disk, |
183 |
-you can use a simplified yaboot.conf. The following should be sufficient: |
184 |
+For POWER4, POWER5, and blade-based hardware where the PReP disk partition and |
185 |
+the disk partition that contains your kernel are on the same physical disk, you |
186 |
+can use a simplified <path>yaboot.conf</path>. The following should be |
187 |
+sufficient: |
188 |
</p> |
189 |
|
190 |
<pre caption="yaboot.conf for PReP hardware"> |
191 |
default = linux |
192 |
timeout = 100 |
193 |
-image=/boot/kernel-2.6.17-gentoo-r5 |
194 |
+image=/boot/<keyval id="kernel-name"/> |
195 |
label=linux |
196 |
read-only |
197 |
root = /dev/sda2 |
198 |
|
199 |
|
200 |
|
201 |
1.17 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml |
202 |
|
203 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.17&view=markup |
204 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.17&content-type=text/plain |
205 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?r1=1.16&r2=1.17 |
206 |
|
207 |
Index: hb-install-ppc64-disk.xml |
208 |
=================================================================== |
209 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v |
210 |
retrieving revision 1.16 |
211 |
retrieving revision 1.17 |
212 |
diff -u -r1.16 -r1.17 |
213 |
--- hb-install-ppc64-disk.xml 14 Mar 2007 07:31:43 -0000 1.16 |
214 |
+++ hb-install-ppc64-disk.xml 1 Apr 2007 23:16:30 -0000 1.17 |
215 |
@@ -4,7 +4,7 @@ |
216 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
217 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
218 |
|
219 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v 1.16 2007/03/14 07:31:43 nightmorph Exp $ --> |
220 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v 1.17 2007/04/01 23:16:30 nightmorph Exp $ --> |
221 |
|
222 |
<sections> |
223 |
|
224 |
@@ -104,11 +104,10 @@ |
225 |
|
226 |
<note> |
227 |
There are some partitions named like this: <path>Apple_Driver43, |
228 |
-Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, |
229 |
-Apple_Patches</path>. If you are not planning to use MacOS 9 you can |
230 |
-delete them, because MacOS X and Linux don't need them. |
231 |
-You might have to use parted in order to delete them, as mac-fdisk can't delete |
232 |
-them yet. |
233 |
+Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If |
234 |
+you are not planning to use MacOS 9 you can delete them, because MacOS X and |
235 |
+Linux don't need them. You might have to use parted in order to delete them, as |
236 |
+mac-fdisk can't delete them yet. |
237 |
</note> |
238 |
|
239 |
<p> |
240 |
@@ -129,14 +128,14 @@ |
241 |
The number of partitions is highly dependent on your environment. For instance, |
242 |
if you have lots of users, you will most likely want to have your |
243 |
<path>/home</path> separate as it increases security and makes backups easier. |
244 |
-If you are installing Gentoo to perform as a mailserver, your |
245 |
-<path>/var</path> should be separate as all mails are stored inside |
246 |
-<path>/var</path>. A good choice of filesystem will then maximise your |
247 |
-performance. Gameservers will have a separate <path>/opt</path> as most gaming |
248 |
-servers are installed there. The reason is similar for <path>/home</path>: |
249 |
-security and backups. You will definitely want to keep <path>/usr</path> big: |
250 |
-not only will it contain the majority of applications, the Portage tree alone |
251 |
-takes around 500 Mbyte excluding the various sources that are stored in it. |
252 |
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
253 |
+should be separate as all mails are stored inside <path>/var</path>. A good |
254 |
+choice of filesystem will then maximise your performance. Gameservers will have |
255 |
+a separate <path>/opt</path> as most gaming servers are installed there. The |
256 |
+reason is similar for <path>/home</path>: security and backups. You will |
257 |
+definitely want to keep <path>/usr</path> big: not only will it contain the |
258 |
+majority of applications, the Portage tree alone takes around 500 Mbyte |
259 |
+excluding the various sources that are stored in it. |
260 |
</p> |
261 |
|
262 |
<p> |
263 |
@@ -164,17 +163,17 @@ |
264 |
</ul> |
265 |
|
266 |
<p> |
267 |
-However, multiple partitions have one big disadvantage: if not configured |
268 |
-properly, you might result in having a system with lots |
269 |
-of free space on one partition and none on another. There is also a 15-partition |
270 |
-limit for SCSI and SATA. |
271 |
+However, multiple partitions have one big disadvantage: if not configured |
272 |
+properly, you might result in having a system with lots of free space on one |
273 |
+partition and none on another. There is also a 15-partition limit for SCSI and |
274 |
+SATA. |
275 |
</p> |
276 |
|
277 |
</body> |
278 |
</subsection> |
279 |
</section> |
280 |
<section id="mac-fdisk"> |
281 |
-<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title> |
282 |
+<title>Default: Using mac-fdisk (Apple G5) to Partition your Disk</title> |
283 |
<body> |
284 |
|
285 |
<p> |
286 |
@@ -225,10 +224,10 @@ |
287 |
|
288 |
<note> |
289 |
To make sure everything is ok, you should run mac-fdisk once more and check |
290 |
-whether all the partitions are there.If you don't see any of the partitions you |
291 |
+whether all the partitions are there. If you don't see any of the partitions you |
292 |
created, or the changes you made, you should reinitialize your partitions by |
293 |
-pressing "i" in mac-fdisk. Note that this will recreate the partition map and |
294 |
-thus remove all your partitions. |
295 |
+pressing <c>i</c> in mac-fdisk. Note that this will recreate the partition map |
296 |
+and thus remove all your partitions. |
297 |
</note> |
298 |
|
299 |
<p> |
300 |
@@ -244,14 +243,14 @@ |
301 |
<body> |
302 |
|
303 |
<note> |
304 |
-If you are planning to use a RAID disk array for your gentoo installation and |
305 |
+If you are planning to use a RAID disk array for your Gentoo installation and |
306 |
you are using POWER5-based hardware, you should now run <c>iprconfig</c> to |
307 |
format the disks to Advanced Function format and create the disk array. You |
308 |
should emerge <c>iprutils</c> after your install is complete. |
309 |
</note> |
310 |
|
311 |
<p> |
312 |
-If you have an ipr based SCSI adapter, you should start the ipr utilities now. |
313 |
+If you have an ipr-based SCSI adapter, you should start the ipr utilities now. |
314 |
</p> |
315 |
|
316 |
<pre caption="Starting ipr utilities"> |
317 |
@@ -647,8 +646,7 @@ |
318 |
|
319 |
<p> |
320 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
321 |
-become production-ready and there hasn't been a sufficient track record to |
322 |
-comment positively nor negatively on its general stability at this point. |
323 |
+become production-ready. |
324 |
</p> |
325 |
|
326 |
</body> |
327 |
@@ -740,7 +738,7 @@ |
328 |
Now that your partitions are initialized and are housing a filesystem, it is |
329 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
330 |
create the necessary mount directories for every partition you created. As an |
331 |
-example we create a mount-point and mount the root and boot partition: |
332 |
+example we create a mount point and mount the root and boot partition: |
333 |
</p> |
334 |
|
335 |
<pre caption="Mounting partitions"> |
336 |
|
337 |
|
338 |
|
339 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml |
340 |
|
341 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?rev=1.15&view=markup |
342 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?rev=1.15&content-type=text/plain |
343 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?r1=1.14&r2=1.15 |
344 |
|
345 |
Index: hb-install-ppc64-kernel.xml |
346 |
=================================================================== |
347 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml,v |
348 |
retrieving revision 1.14 |
349 |
retrieving revision 1.15 |
350 |
diff -u -r1.14 -r1.15 |
351 |
--- hb-install-ppc64-kernel.xml 19 Mar 2007 08:20:15 -0000 1.14 |
352 |
+++ hb-install-ppc64-kernel.xml 1 Apr 2007 23:16:30 -0000 1.15 |
353 |
@@ -4,7 +4,7 @@ |
354 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
355 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
356 |
|
357 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml,v 1.14 2007/03/19 08:20:15 nightmorph Exp $ --> |
358 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml,v 1.15 2007/04/01 23:16:30 nightmorph Exp $ --> |
359 |
|
360 |
<sections> |
361 |
|
362 |
@@ -57,13 +57,13 @@ |
363 |
<p> |
364 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
365 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
366 |
-kernel source points to <c>gentoo-sources-2.6.17-r5</c>. Your version may be |
367 |
-different, so keep this in mind. |
368 |
+kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>. |
369 |
+Your version may be different, so keep this in mind. |
370 |
</p> |
371 |
|
372 |
<pre caption="Viewing the kernel source symlink"> |
373 |
# <i>ls -l /usr/src/linux</i> |
374 |
-lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.17-gentoo-r5 |
375 |
+lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
376 |
</pre> |
377 |
|
378 |
<p> |
379 |
@@ -107,8 +107,8 @@ |
380 |
<pre caption="Invoking menuconfig"> |
381 |
# <i>cd /usr/src/linux</i> |
382 |
<comment>Important: In case you are in 32-bit userland, you must edit the top |
383 |
-level Makefile in /usr/src/linux and change the CROSS_COMPILE option to |
384 |
-CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run |
385 |
+level Makefile in /usr/src/linux and change the CROSS_COMPILE option to |
386 |
+CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run |
387 |
make menuconfig or it may result in kernel compilation problems.</comment> |
388 |
# <i>make menuconfig</i> |
389 |
</pre> |
390 |
|
391 |
|
392 |
|
393 |
1.23 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml |
394 |
|
395 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?rev=1.23&view=markup |
396 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?rev=1.23&content-type=text/plain |
397 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?r1=1.22&r2=1.23 |
398 |
|
399 |
Index: hb-install-ppc64-medium.xml |
400 |
=================================================================== |
401 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml,v |
402 |
retrieving revision 1.22 |
403 |
retrieving revision 1.23 |
404 |
diff -u -r1.22 -r1.23 |
405 |
--- hb-install-ppc64-medium.xml 19 Mar 2007 10:26:44 -0000 1.22 |
406 |
+++ hb-install-ppc64-medium.xml 1 Apr 2007 23:16:30 -0000 1.23 |
407 |
@@ -4,7 +4,7 @@ |
408 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
409 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
410 |
|
411 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml,v 1.22 2007/03/19 10:26:44 nightmorph Exp $ --> |
412 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml,v 1.23 2007/04/01 23:16:30 nightmorph Exp $ --> |
413 |
|
414 |
<sections> |
415 |
|
416 |
@@ -87,8 +87,7 @@ |
417 |
<p> |
418 |
If you wish to install Gentoo without a working Internet connection, please use |
419 |
the installation instructions described in the <uri |
420 |
-link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>. This is currently not |
421 |
-supported for the PPC64 architecture though. |
422 |
+link="2007.0/index.xml">Gentoo 2007.0 Handbooks</uri>. |
423 |
</p> |
424 |
|
425 |
<p> |
426 |
@@ -210,10 +209,10 @@ |
427 |
</p> |
428 |
|
429 |
<p> |
430 |
-You can download any of the Installation CDs (and, if you want to, a Packages |
431 |
-CD as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The |
432 |
-Installation CDs are located in the |
433 |
-<path>releases/ppc/2007.0/ppc64/installcd</path> directory. |
434 |
+You can download any of the Installation CDs (and, if you want to, a Packages CD |
435 |
+as well) from one of our <uri link="/main/en/mirrors.xml">mirrors</uri>. The |
436 |
+Installation CDs are located in the <path><keyval |
437 |
+id="release-dir"/>installcd</path> directory. |
438 |
</p> |
439 |
|
440 |
<p> |
441 |
@@ -306,15 +305,15 @@ |
442 |
This option takes one of the following vendor-specific tags: |
443 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c> |
444 |
or <c>ofonly</c>. You can follow this tag with the resolution and |
445 |
- refreshrate you want to use. For instance <c>video=radeonfb:1280x1024@75</c> |
446 |
- . If you are uncertain what to choose, <c>ofonly</c> will most certainly |
447 |
- work. |
448 |
+ refreshrate you want to use. For instance |
449 |
+ <c>video=radeonfb:1280x1024@75</c>. If you are uncertain what to choose, |
450 |
+ <c>ofonly</c> will most certainly work. |
451 |
</ti> |
452 |
</tr> |
453 |
<tr> |
454 |
<ti><c>nol3</c></ti> |
455 |
<ti> |
456 |
- Disables level 3 cache on some powerbooks (needed for at least the 17'') |
457 |
+ Disables level 3 cache on some powerbooks (needed for at least the 17") |
458 |
</ti> |
459 |
</tr> |
460 |
<tr> |
461 |
@@ -433,11 +432,11 @@ |
462 |
|
463 |
<p> |
464 |
When the Installation CD boots, it tries to detect all your hardware devices and |
465 |
-loads the appropriate kernel modules to support your hardware. In the |
466 |
-vast majority of cases, it does a very good job. However, in some cases it may |
467 |
-not auto-load the kernel |
468 |
-modules you need. If the PCI auto-detection missed some of your system's |
469 |
-hardware, you will have to load the appropriate kernel modules manually. |
470 |
+loads the appropriate kernel modules to support your hardware. In the vast |
471 |
+majority of cases, it does a very good job. However, in some cases it may not |
472 |
+auto-load the kernel modules you need. If the PCI auto-detection missed some of |
473 |
+your system's hardware, you will have to load the appropriate kernel modules |
474 |
+manually. |
475 |
</p> |
476 |
|
477 |
<p> |
478 |
@@ -473,8 +472,10 @@ |
479 |
</p> |
480 |
|
481 |
<pre caption="Tweaking hard disk performance"> |
482 |
-<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
483 |
-<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
484 |
+<comment>Activate DMA:</comment> |
485 |
+# <i>hdparm -d 1 /dev/hda</i> |
486 |
+<comment>Activate DMA + Safe Performance-enhancing Options:</comment> |
487 |
+# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
488 |
</pre> |
489 |
|
490 |
</body> |
491 |
|
492 |
|
493 |
|
494 |
-- |
495 |
gentoo-doc-cvs@g.o mailing list |