From: "Josh Saddler" <nightmorph@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml
Date: Mon, 18 Sep 2006 06:53:41 +0000 [thread overview]
Message-ID: <20060918065342.15B916466A@smtp.gentoo.org> (raw)
nightmorph 06/09/18 06:53:41
Modified: gentoo-amd64-faq.xml
Log:
several typo/capitalization fixes; **no content change**
Revision Changes Path
1.17 xml/htdocs/doc/en/gentoo-amd64-faq.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?r1=1.16&r2=1.17
Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- gentoo-amd64-faq.xml 17 Jun 2006 07:04:43 -0000 1.16
+++ gentoo-amd64-faq.xml 18 Sep 2006 06:53:41 -0000 1.17
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.16 2006/06/17 07:04:43 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.17 2006/09/18 06:53:41 nightmorph Exp $ -->
<guide link="/doc/en/gentoo-amd64-faq.xml">
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
@@ -38,7 +38,7 @@
<p>
This document contains the most commonly asked questions about Gentoo/AMD64. We
intend to help and provide useful information about Gentoo/AMD64. Some of these
-questions can be found in forums, irc, or mailing lists. If you have suggestions
+questions can be found in forums, IRC, or mailing lists. If you have suggestions
or questions about this FAQ, you are welcome to send an e-mail to the authors
explaining the problem.
</p>
@@ -53,7 +53,7 @@
<li><uri link="#cflags">What CFLAGS should I use for AMD64/EM64T?</uri></li>
<li><uri link="#kernel">What kernel should I use?</uri></li>
<li>
- <uri link="#perfup">Will I have a performance upgrade if I use 64-bit
+ <uri link="#perfup">Will I have a performance upgrade if I use a 64-bit
system instead of 32-bit?</uri>
</li>
<li>
@@ -79,7 +79,7 @@
<uri link="#videobindrivers">Will my binary NVIDIA/ATI drivers work?</uri>
</li>
<li>
- <uri link="#coolnquiet">How do I use Cool'n'Quiet/Powernow features?</uri>
+ <uri link="#coolnquiet">How do I use Cool'n'Quiet/PowerNow features?</uri>
</li>
</ul>
@@ -140,9 +140,9 @@
<p>
You should use simple <c>CFLAGS</c> to avoid future problems with your system.
For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
-Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If
-you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp
--O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
+Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for an EM64T processor. If
+you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp -O2
+-pipe -msse2"</c> for an AMD64 processor; for an EM64T, you should use
<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
</p>
@@ -180,7 +180,7 @@
</body>
</section>
<section id="perfup">
-<title>Will I have a performance upgrade if I use 64-bit system instead of 32-bit?</title>
+<title>Will I have a performance upgrade if I use a64-bit system instead of 32-bit?</title>
<body>
<p>
@@ -275,6 +275,7 @@
Reiser4 is not available from any kernel offered by the Gentoo Kernel project,
thus neither AMD64 team supports it. The answer is no.
</p>
+
</body>
</section>
</chapter>
@@ -296,7 +297,7 @@
</body>
</section>
<section id="coolnquiet">
-<title>How do I use Cool'n'Quiet/Powernow features?</title>
+<title>How do I use Cool'n'Quiet/PowerNow features?</title>
<body>
<p>
@@ -304,7 +305,7 @@
to enable the features below:
</p>
-<pre caption="Kernel options for Cool'n'Quiet/Powernow">
+<pre caption="Kernel options for Cool'n'Quiet/PowerNow">
Power management options --->
[*] Power Management support
CPU Frequency scaling --->
@@ -346,7 +347,7 @@
Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>,
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
64-bit version. After emerging the -bin-package of your favorite browser,
-install flash by doing <c>emerge netscape-flash</c>.
+install Flash by doing <c>emerge netscape-flash</c>.
</p>
</body>
@@ -357,7 +358,7 @@
<p>
OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the
-32-bit binary version, available in portage as <c>openoffice-bin</c>.
+32-bit binary version, available in Portage as <c>openoffice-bin</c>.
</p>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-09-18 6:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 6:53 Josh Saddler [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 19:46 [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml Joshua Saddler
2008-09-02 7:47 Joshua Saddler
2008-07-25 18:55 Joshua Saddler
2008-05-21 20:10 Sven Vermeulen
2006-11-24 14:47 Josh Saddler
2006-10-25 12:54 Xavier Neys
2006-10-06 22:01 Josh Saddler
2006-10-05 0:00 Josh Saddler
2006-10-04 14:23 Xavier Neys
2006-09-18 8:25 Josh Saddler
2006-06-17 7:04 Shyam Mani
2006-03-28 10:20 Xavier Neys
2006-03-19 22:26 Jan Kundrat
2006-02-26 13:56 Xavier Neys
2006-02-17 18:48 Shyam Mani
2006-02-11 14:22 swift
2006-02-01 9:45 Shyam Mani
2005-12-13 12:17 Xavier Neys
2005-11-23 18:06 Xavier Neys
2005-10-31 13:31 Xavier Neys
2005-09-20 9:13 Lukasz Damentko
2005-09-19 21:50 Lukasz Damentko
2005-08-07 11:15 Alin Dobre
2005-07-16 15:14 Jonathan Smith
2005-07-16 15:08 Jonathan Smith
2005-07-16 9:44 Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060918065342.15B916466A@smtp.gentoo.org \
--to=nightmorph@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox