nightmorph 07/04/01 23:16:09
Modified: hb-install-ppc64-bootloader.xml
hb-install-ppc64-disk.xml
hb-install-ppc64-kernel.xml
hb-install-ppc64-medium.xml
Log:
ppc64 done
Revision Changes Path
1.2
xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml?rev=1.2&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml?rev=1.2&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml?r1=1.1&r2=1.2
Index: hb-install-ppc64-bootloader.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ppc64-bootloader.xml 19 Mar 2007 20:37:28 -0000 1.1
+++ hb-install-ppc64-bootloader.xml 1 Apr 2007 23:16:09 -0000 1.2
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml,v
1.1 2007/03/19 20:37:28 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml,v
1.2 2007/04/01 23:16:09 nightmorph Exp $ -->
<sections>
-<version>7.0</version>
+<version>8.0</version>
<date>2006-08-30</date>
<section>
@@ -45,34 +45,19 @@
</impo>
<p>
-There are two ways to configure yaBoot for your system. You can use the
-new and improved <c>yabootconfig</c> included with
-<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If
-for some reason you do not want to run <c>yabootconfig</c> to
-automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo
-on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit
-the sample file already installed on your system.
+There are two ways to configure yaBoot for your system. You can use the new and
+improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and
+later to automatically set up yaboot. If for some reason you do not want to run
+<c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or
you
+are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always
+work), you can just edit the sample file already installed on your system.
</p>
-<impo>
-If you are installing on a G5 using an online install and have not used the
-G5 optimized stages you must change what profile you are linked to now. If you
-do not you will not get dependencies necessary for yaboot to run on Apple
-equipment. In the command below replace <c>(userland)</c> with your chosen
-userland bit level. If you are installing on a G5 using an offline install
-you have to install these packages by hand.
-</impo>
-
-<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile">
-# <i>rm /etc/make.profile</i>
-# <i>ln -sf
/usr/portage/profiles/default-linux/ppc/2006.1/ppc64/(userland)/970/pmac
/etc/make.profile</i>
-</pre>
-
-<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File
System Tools">
+<pre caption="Installing Necessary File System Tools">
# <i>emerge hfsutils hfsplusutils</i>
</pre>
-<pre caption = "Installing the bootloader">
+<pre caption="Installing the bootloader">
<comment>(64bit userland)</comment>
# <i>emerge --update yaboot-static</i>
<comment>(32bit userland)</comment>
@@ -111,7 +96,7 @@
<p>
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and
-<path>/etc/fstab</path> must be configured with your Linux partitions. Both of
+<path>/etc/fstab</path> must be configured with your Linux partitions. Both of
these should have been done already in the steps above. To start, ensure that
you have the latest version of yaboot installed by running <c>emerge --update
yaboot-static</c>. This is necessary as the latest version will be available
via
@@ -119,12 +104,12 @@
</p>
<p>
-Now run <c>yabootconfig</c>. The program will run and it will confirm
-the location of the bootstrap partition. Type <c>Y</c> if it is correct. If
-not, double check <path>/etc/fstab</path>. yabootconfig will then scan your
-system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for
-you. <c>mkofboot</c> is used to format the bootstrap partition, and install
-the yaboot configuration file into it.
+Now run <c>yabootconfig</c>. The program will run and it will confirm the
+location of the bootstrap partition. Type <c>Y</c> if it is correct. If not,
+double check <path>/etc/fstab</path>. yabootconfig will then scan your system
+setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you.
+<c>mkofboot</c> is used to format the bootstrap partition, and install the
+yaboot configuration file into it.
</p>
<p>
@@ -149,7 +134,7 @@
will.
</p>
-<pre caption = "/etc/yaboot.conf">
+<pre caption="/etc/yaboot.conf">
<comment>## /etc/yaboot.conf
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
@@ -180,9 +165,9 @@
<comment>#################
## This section can be duplicated if you have more than one kernel or set of
-## boot options - replace 2.6.17-gentoo-r5 with your kernel-version
+## boot options - replace <keyval id="kernel-name"/> with your kernel-version
#################</comment>
-image=/boot/kernel-2.6.17-gentoo-r5
+image=/boot/<keyval id="kernel-name"/>
label=Linux
root=/dev/hda3
partition=3
@@ -195,25 +180,22 @@
</pre>
<p>
-Once <path>yaboot.conf</path> is set up the way you want it, you run
-<c>mkofboot -v</c> to install the settings in the bootstrap partition.
-<e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new
-filesystem.
+Once <path>yaboot.conf</path> is set up the way you want it, you run
<c>mkofboot
+-v</c> to install the settings in the bootstrap partition. <e>Don't forget
+this!</e> Confirm when <c>mkofboot</c> asks you to create a new filesystem.
</p>
<p>
-If all goes well, and you have the same
-options as the sample above, your next reboot will give you a simple,
-five-entry boot menu. If you update your yaboot config later on, you'll
-just need to run <c>ybin -v</c> to update the bootstrap partition -
-<c>mkofboot</c> is for initial setup only.
+If all goes well, and you have the same options as the sample above, your next
+reboot will give you a simple, five-entry boot menu. If you update your yaboot
+config later on, you'll just need to run <c>ybin -v</c> to update the bootstrap
+partition - <c>mkofboot</c> is for initial setup only.
</p>
<p>
For more information on yaboot, take a look at the <uri
-link="http://penguinppc.org/projects/yaboot";>yaboot project</uri>. For
-now, continue the installation with <uri link="#reboot">Rebooting your
-System</uri>.
+link="http://penguinppc.org/projects/yaboot";>yaboot project</uri>. For now,
+continue the installation with <uri link="#reboot">Rebooting your System</uri>.
</p>
</body>
@@ -224,48 +206,56 @@
<body>
<p>
-On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the
+On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the
following steps:
</p>
<ul>
<li>Install yaboot-static</li>
- <li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX
- with your disk and partition for the PReP partition; this was in our
- example /dev/sda1)</li>
- <li>Next construct your own yaboot.conf file and place into /etc.
- (Take a look at the config above, look into the man page of
- yaboot.conf or look at the below yaboot.conf example)</li>
- <li>Assuming your boot device in OF is pointing to the harddrive you
- prep boot partition is on then it'll just work, otherwise at IPL time,
- go into the multiboot menu and set the boot device to the one with
- your prep boot partition.</li>
+ <li>
+ Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with
+ your disk and partition for the PReP partition; this was in our example
+ <path>/dev/sda1</path>)
+ </li>
+ <li>
+ Next construct your own <path>yaboot.conf</path> file and place into
+ <path>/etc</path>. (Take a look at the config above, look into the man page
+ of <path>yaboot.conf</path> or look at the below <path>yaboot.conf</path>
+ example.)
+ </li>
+ <li>
+ Assuming your boot device in OF is pointing to the harddrive you prep boot
+ partition is on then it'll just work, otherwise at IPL time, go into the
+ multiboot menu and set the boot device to the one with your prep boot
+ partition
+ </li>
<li>That's it!</li>
</ul>
-<pre caption = "yaboot.conf for IBM hardware">
+<pre caption="yaboot.conf for IBM hardware">
device=disk:
partition=2
root=/dev/sda2
-default=2.6.17-gentoo-r5
+default=linux
timeout=50
-image=/boot/kernel-2.6.17-gentoo-r5
- label=Linux
+image=/boot/<keyval id="kernel-name"/>
+ label=linux
append="console=ttyS0,9600"
read-only
</pre>
<p>
-For POWER4, POWER5, and blade-based hardware where the PReP disk partition
-and the disk partition that contains your kernel are on the same physical disk,
-you can use a simplified yaboot.conf. The following should be sufficient:
+For POWER4, POWER5, and blade-based hardware where the PReP disk partition and
+the disk partition that contains your kernel are on the same physical disk, you
+can use a simplified <path>yaboot.conf</path>. The following should be
+sufficient:
</p>
<pre caption="yaboot.conf for PReP hardware">
default = linux
timeout = 100
-image=/boot/kernel-2.6.17-gentoo-r5
+image=/boot/<keyval id="kernel-name"/>
label=linux
read-only
root = /dev/sda2
1.2 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml?rev=1.2&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml?rev=1.2&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml?r1=1.1&r2=1.2
Index: hb-install-ppc64-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ppc64-disk.xml 19 Mar 2007 20:37:28 -0000 1.1
+++ hb-install-ppc64-disk.xml 1 Apr 2007 23:16:09 -0000 1.2
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml,v
1.1 2007/03/19 20:37:28 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml,v
1.2 2007/04/01 23:16:09 nightmorph Exp $ -->
<sections>
-<version>7.1</version>
+<version>8.0</version>
<date>2006-11-02</date>
<section>
@@ -104,10 +104,10 @@
<note>
There are some partitions named like this: <path>Apple_Driver43,
-Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit,
-Apple_Patches</path>. If you are not planning to use MacOS 9 you can
-delete them, because MacOS X and Linux don't need them.
-You might have to use parted in order to delete them, as mac-fdisk can't
delete them yet.
+Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If
+you are not planning to use MacOS 9 you can delete them, because MacOS X and
+Linux don't need them. You might have to use parted in order to delete them,
as
+mac-fdisk can't delete them yet.
</note>
<p>
@@ -128,14 +128,14 @@
The number of partitions is highly dependent on your environment. For instance,
if you have lots of users, you will most likely want to have your
<path>/home</path> separate as it increases security and makes backups easier.
-If you are installing Gentoo to perform as a mailserver, your
-<path>/var</path> should be separate as all mails are stored inside
-<path>/var</path>. A good choice of filesystem will then maximise your
-performance. Gameservers will have a separate <path>/opt</path> as most gaming
-servers are installed there. The reason is similar for <path>/home</path>:
-security and backups. You will definitely want to keep <path>/usr</path> big:
-not only will it contain the majority of applications, the Portage tree alone
-takes around 500 Mbyte excluding the various sources that are stored in it.
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
+should be separate as all mails are stored inside <path>/var</path>. A good
+choice of filesystem will then maximise your performance. Gameservers will have
+a separate <path>/opt</path> as most gaming servers are installed there. The
+reason is similar for <path>/home</path>: security and backups. You will
+definitely want to keep <path>/usr</path> big: not only will it contain the
+majority of applications, the Portage tree alone takes around 500 Mbyte
+excluding the various sources that are stored in it.
</p>
<p>
@@ -157,23 +157,23 @@
it is with multiple partitions)
</li>
<li>
- Security can be enhanced by mounting some partitions or volumes read-only,
+ Security can be enhanced by mounting some partitions or volumes read-only,
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
</li>
</ul>
<p>
-However, multiple partitions have one big disadvantage: if not configured
-properly, you might result in having a system with lots
-of free space on one partition and none on another. There is also a
15-partition
-limit for SCSI and SATA.
+However, multiple partitions have one big disadvantage: if not configured
+properly, you might result in having a system with lots of free space on one
+partition and none on another. There is also a 15-partition limit for SCSI and
+SATA.
</p>
</body>
</subsection>
</section>
<section id="mac-fdisk">
-<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title>
+<title>Default: Using mac-fdisk (Apple G5) to Partition your Disk</title>
<body>
<p>
@@ -223,9 +223,11 @@
</p>
<note>
-To make sure everything is ok, you should run mac-fdisk once more and check
whether all the partitions are there.
-If you don't see any of the partitions you created, or the changes you made,
you should reinitialize your partitions by pressing "i" in mac-fdisk.
-Note that this will recreate the partition map and thus remove all your
partitions.
+To make sure everything is ok, you should run mac-fdisk once more and check
+whether all the partitions are there. If you don't see any of the partitions
you
+created, or the changes you made, you should reinitialize your partitions by
+pressing <c>i</c> in mac-fdisk. Note that this will recreate the partition map
+and thus remove all your partitions.
</note>
<p>
@@ -241,14 +243,14 @@
<body>
<note>
-If you are planning to use a RAID disk array for your gentoo installation and
+If you are planning to use a RAID disk array for your Gentoo installation and
you are using POWER5-based hardware, you should now run <c>iprconfig</c> to
format the disks to Advanced Function format and create the disk array. You
should emerge <c>iprutils</c> after your install is complete.
</note>
<p>
-If you have an ipr based SCSI adapter, you should start the ipr utilities now.
+If you have an ipr-based SCSI adapter, you should start the ipr utilities now.
</p>
<pre caption="Starting ipr utilities">
@@ -704,11 +706,13 @@
<p>
Now that your partitions are initialized and are housing a filesystem, it is
-time to mount those partitions. Use the <c>mount</c> command. As an example we
-mount the root partition:
+time to mount those partitions. Use the <c>mount</c> command. Don't forget to
+create the necessary mount directories for every partition you created. As an
+example we create a mount point and mount the root and boot partition:
</p>
<pre caption="Mounting partitions">
+# <i>mkdir /mnt/gentoo</i>
# <i>mount /dev/sda4 /mnt/gentoo</i>
</pre>
1.2
xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml?rev=1.2&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml?rev=1.2&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml?r1=1.1&r2=1.2
Index: hb-install-ppc64-kernel.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-ppc64-kernel.xml 19 Mar 2007 20:37:28 -0000 1.1
+++ hb-install-ppc64-kernel.xml 1 Apr 2007 23:16:09 -0000 1.2
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml,v
1.1 2007/03/19 20:37:28 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml,v
1.2 2007/04/01 23:16:09 nightmorph Exp $ -->
<sections>
-<version>7.1</version>
+<version>8.0</version>
<date>2007-02-26</date>
<section>
@@ -17,8 +17,8 @@
<p>
You first need to select your timezone so that your system knows where it is
-located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
-it to <path>/etc/localtime</path>. Please avoid the
+located. Look for your timezone in <path>/usr/share/zoneinfo</path>. You then
+set your timezone in <path>/etc/conf.d/clock</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8.
</p>
@@ -26,7 +26,8 @@
<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
-# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
+# <i>nano -w /etc/conf.d/clock</i>
+TIMEZONE="GMT"
</pre>
</body>
@@ -56,13 +57,13 @@
<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
-kernel source points to <c>gentoo-sources-2.6.17-r5</c>. Your version may be
-different, so keep this in mind.
+kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
+Your version may be different, so keep this in mind.
</p>
<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx 1 root root 12 Aug 10 11:04 /usr/src/linux ->
linux-2.6.17-gentoo-r5
+lrwxrwxrwx 1 root root 12 Aug 10 11:04 /usr/src/linux ->
linux-<keyval id="kernel-version"/>
</pre>
<p>
@@ -136,11 +137,10 @@
</pre>
<p>
-Now go to <c>File Systems</c> and select support for the filesystems you
-use. <e>Don't</e> compile them as modules, otherwise your Gentoo system
-will not be able to mount your partitions. Also select <c>Virtual
-memory</c>, <c>/proc file system</c>, and <c>/dev/pts file system for
-Unix98 PTYs</c>:
+Now go to <c>File Systems</c> and select support for the filesystems you use.
+<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
+able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc file
+system</c>, and <c>/dev/pts file system for Unix98 PTYs</c>:
</p>
<pre caption="Selecting necessary file systems">
1.3
xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml?rev=1.3&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml?rev=1.3&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml?r1=1.2&r2=1.3
Index: hb-install-ppc64-medium.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- hb-install-ppc64-medium.xml 20 Mar 2007 05:31:13 -0000 1.2
+++ hb-install-ppc64-medium.xml 1 Apr 2007 23:16:09 -0000 1.3
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml,v
1.2 2007/03/20 05:31:13 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml,v
1.3 2007/04/01 23:16:09 nightmorph Exp $ -->
<sections>
-<version>7.0</version>
+<version>8.0</version>
<date>2006-08-30</date>
<section>
@@ -137,11 +137,10 @@
<p>
You can download the Universal Installation CD (and, if you want to, the
-Packages CD as well) from one of our <uri
-link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located
-in the <path>releases/ppc/2007.0/ppc64/installcd</path> directory; the Package
-CDs are located in the <path>releases/ppc/2007.0/ppc64/packagecd</path>
-directory.
+Packages CD as well) from one of our <uri
+link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in
+the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs
+are located in the <path><keyval id="release-dir"/>packagecd</path> directory.
</p>
<p>
@@ -236,16 +235,16 @@
<ti>
This option takes one of the following vendor-specific tags:
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>,
<c>nvidiafb</c>
- or <c>ofonly</c>. You can follow this tag with the resolution and
- refreshrate you want to use. For instance <c>video=radeonfb:[EMAIL
PROTECTED]</c>
- . If you are uncertain what to choose, <c>ofonly</c> will most certainly
- work.
+ or <c>ofonly</c>. You can follow this tag with the resolution and
+ refreshrate you want to use. For instance
+ <c>video=radeonfb:[EMAIL PROTECTED]</c>. If you are uncertain what to
choose,
+ <c>ofonly</c> will most certainly work.
</ti>
</tr>
<tr>
<ti><c>nol3</c></ti>
<ti>
- Disables level 3 cache on some powerbooks (needed for at least the 17'')
+ Disables level 3 cache on some powerbooks (needed for at least the 17")
</ti>
</tr>
<tr>
@@ -351,11 +350,11 @@
<p>
When the Installation CD boots, it tries to detect all your hardware devices
and
-loads the appropriate kernel modules to support your hardware. In the
-vast majority of cases, it does a very good job. However, in some cases it may
-not auto-load the kernel
-modules you need. If the PCI auto-detection missed some of your system's
-hardware, you will have to load the appropriate kernel modules manually.
+loads the appropriate kernel modules to support your hardware. In the vast
+majority of cases, it does a very good job. However, in some cases it may not
+auto-load the kernel modules you need. If the PCI auto-detection missed some of
+your system's hardware, you will have to load the appropriate kernel modules
+manually.
</p>
<p>
@@ -391,8 +390,10 @@
</p>
<pre caption="Tweaking hard disk performance">
-<comment>Activate DMA:</comment> #
<i>hdparm -d 1 /dev/hda</i>
-<comment>Activate DMA + Safe Performance-enhancing Options:</comment> #
<i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
+<comment>Activate DMA:</comment>
+# <i>hdparm -d 1 /dev/hda</i>
+<comment>Activate DMA + Safe Performance-enhancing Options:</comment>
+# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i>
</pre>
</body>
@@ -467,7 +468,7 @@
</p>
<pre caption="Viewing the Online Documentation">
-# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i>
+# <i>links http://www.gentoo.org/doc/en/handbook/2007.0/handbook-ppc64.xml</i>
</pre>
<p>
--
[email protected] mailing list
