| 1 |
nightmorph 06/09/18 06:53:41 |
| 2 |
|
| 3 |
Modified: gentoo-amd64-faq.xml |
| 4 |
Log: |
| 5 |
several typo/capitalization fixes; **no content change** |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.17 xml/htdocs/doc/en/gentoo-amd64-faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.17&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.17&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?r1=1.16&r2=1.17 |
| 13 |
|
| 14 |
Index: gentoo-amd64-faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v |
| 17 |
retrieving revision 1.16 |
| 18 |
retrieving revision 1.17 |
| 19 |
diff -u -r1.16 -r1.17 |
| 20 |
--- gentoo-amd64-faq.xml 17 Jun 2006 07:04:43 -0000 1.16 |
| 21 |
+++ gentoo-amd64-faq.xml 18 Sep 2006 06:53:41 -0000 1.17 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.16 2006/06/17 07:04:43 fox2mike Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.17 2006/09/18 06:53:41 nightmorph Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/gentoo-amd64-faq.xml"> |
| 29 |
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title> |
| 30 |
@@ -38,7 +38,7 @@ |
| 31 |
<p> |
| 32 |
This document contains the most commonly asked questions about Gentoo/AMD64. We |
| 33 |
intend to help and provide useful information about Gentoo/AMD64. Some of these |
| 34 |
-questions can be found in forums, irc, or mailing lists. If you have suggestions |
| 35 |
+questions can be found in forums, IRC, or mailing lists. If you have suggestions |
| 36 |
or questions about this FAQ, you are welcome to send an e-mail to the authors |
| 37 |
explaining the problem. |
| 38 |
</p> |
| 39 |
@@ -53,7 +53,7 @@ |
| 40 |
<li><uri link="#cflags">What CFLAGS should I use for AMD64/EM64T?</uri></li> |
| 41 |
<li><uri link="#kernel">What kernel should I use?</uri></li> |
| 42 |
<li> |
| 43 |
- <uri link="#perfup">Will I have a performance upgrade if I use 64-bit |
| 44 |
+ <uri link="#perfup">Will I have a performance upgrade if I use a 64-bit |
| 45 |
system instead of 32-bit?</uri> |
| 46 |
</li> |
| 47 |
<li> |
| 48 |
@@ -79,7 +79,7 @@ |
| 49 |
<uri link="#videobindrivers">Will my binary NVIDIA/ATI drivers work?</uri> |
| 50 |
</li> |
| 51 |
<li> |
| 52 |
- <uri link="#coolnquiet">How do I use Cool'n'Quiet/Powernow features?</uri> |
| 53 |
+ <uri link="#coolnquiet">How do I use Cool'n'Quiet/PowerNow features?</uri> |
| 54 |
</li> |
| 55 |
</ul> |
| 56 |
|
| 57 |
@@ -140,9 +140,9 @@ |
| 58 |
<p> |
| 59 |
You should use simple <c>CFLAGS</c> to avoid future problems with your system. |
| 60 |
For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or |
| 61 |
-Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If |
| 62 |
-you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp |
| 63 |
--O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use |
| 64 |
+Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for an EM64T processor. If |
| 65 |
+you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp -O2 |
| 66 |
+-pipe -msse2"</c> for an AMD64 processor; for an EM64T, you should use |
| 67 |
<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>. |
| 68 |
</p> |
| 69 |
|
| 70 |
@@ -180,7 +180,7 @@ |
| 71 |
</body> |
| 72 |
</section> |
| 73 |
<section id="perfup"> |
| 74 |
-<title>Will I have a performance upgrade if I use 64-bit system instead of 32-bit?</title> |
| 75 |
+<title>Will I have a performance upgrade if I use a64-bit system instead of 32-bit?</title> |
| 76 |
<body> |
| 77 |
|
| 78 |
<p> |
| 79 |
@@ -275,6 +275,7 @@ |
| 80 |
Reiser4 is not available from any kernel offered by the Gentoo Kernel project, |
| 81 |
thus neither AMD64 team supports it. The answer is no. |
| 82 |
</p> |
| 83 |
+ |
| 84 |
</body> |
| 85 |
</section> |
| 86 |
</chapter> |
| 87 |
@@ -296,7 +297,7 @@ |
| 88 |
</body> |
| 89 |
</section> |
| 90 |
<section id="coolnquiet"> |
| 91 |
-<title>How do I use Cool'n'Quiet/Powernow features?</title> |
| 92 |
+<title>How do I use Cool'n'Quiet/PowerNow features?</title> |
| 93 |
<body> |
| 94 |
|
| 95 |
<p> |
| 96 |
@@ -304,7 +305,7 @@ |
| 97 |
to enable the features below: |
| 98 |
</p> |
| 99 |
|
| 100 |
-<pre caption="Kernel options for Cool'n'Quiet/Powernow"> |
| 101 |
+<pre caption="Kernel options for Cool'n'Quiet/PowerNow"> |
| 102 |
Power management options ---> |
| 103 |
[*] Power Management support |
| 104 |
CPU Frequency scaling ---> |
| 105 |
@@ -346,7 +347,7 @@ |
| 106 |
Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>, |
| 107 |
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a |
| 108 |
64-bit version. After emerging the -bin-package of your favorite browser, |
| 109 |
-install flash by doing <c>emerge netscape-flash</c>. |
| 110 |
+install Flash by doing <c>emerge netscape-flash</c>. |
| 111 |
</p> |
| 112 |
|
| 113 |
</body> |
| 114 |
@@ -357,7 +358,7 @@ |
| 115 |
|
| 116 |
<p> |
| 117 |
OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the |
| 118 |
-32-bit binary version, available in portage as <c>openoffice-bin</c>. |
| 119 |
+32-bit binary version, available in Portage as <c>openoffice-bin</c>. |
| 120 |
</p> |
| 121 |
|
| 122 |
</body> |
| 123 |
|
| 124 |
|
| 125 |
|
| 126 |
-- |
| 127 |
gentoo-doc-cvs@g.o mailing list |
Archives