[gentoo-doc-cvs] cvs commit: gentoo-mips-faq.xml

["swift" <swift@lark.gentoo.org>]

swift       05/08/30 19:04:02

  Modified:    xml/htdocs/doc/en/draft gentoo-mips-faq.xml
  Log:
  Last few changes

Revision  Changes    Path
1.5       +14 -11    xml/htdocs/doc/en/draft/gentoo-mips-faq.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo

Index: gentoo-mips-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- gentoo-mips-faq.xml	9 Aug 2005 13:55:27 -0000	1.4
+++ gentoo-mips-faq.xml	30 Aug 2005 19:04:02 -0000	1.5
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml,v 1.4 2005/08/09 13:55:27 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml,v 1.5 2005/08/30 19:04:02 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/draft/gentoo-mips-faq.xml">
@@ -20,7 +20,7 @@
 <license/>
 
 <version>1.0</version>
-<date>2005-08-09</date>
+<date>2005-08-30</date>
 
 <chapter>
 <title>About this document</title>
@@ -336,9 +336,9 @@
 
 <p>
 For the first one an easy way to find out is to have a look at the
-<uri link="http://www.gentoo.org/doc/en/mips-requirements.xml">Gentoo/MIPS
+<uri link="/doc/en/mips-requirements.xml">Gentoo/MIPS
 requirements page</uri>.  This will tell you if the system you've got can
-theoretically run Gentoo/MIPS.  I've also written a
+theoretically run Gentoo/MIPS.  Stuart has also written a
 <uri link="http://stuartl.longlandclan.hopto.org/gentoo/mips/">hardware support
 database</uri> in which users may contribute their experiences.  This can help
 measure how well Gentoo/MIPS runs on a particular machine.
@@ -362,7 +362,7 @@
 <p>
 If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably
 noticed there are a LOT of machines we don't support.  In the case of SGI
-hardware, on some of the machines very little is known about them, not enough
+hardware, very little is known about some of them, not enough
 to successfully port Linux to them.
 </p>
 
@@ -405,7 +405,10 @@
 
 <p>
 So for those of you who are running R4000-class CPUs, try a <c>mips3</c> or
-<c>mipsel3</c> stage tarball.<br />
+<c>mipsel3</c> stage tarball.
+</p>
+
+<p>
 For those running R5000-class or later CPUs, try a <c>mips4</c> or
 <c>mipsel4</c> stage tarball.
 </p>
@@ -427,10 +430,10 @@
 
 <p>
 This is generally caused by using the wrong stage tarball.  If you try to run a
-<c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <c>illegal
-instruction</c> error message.  Likewise, if you have a Big Endian CPU and you
-try running Little Endian code on it, you'll get told <c>cannot execute binary
-file</c>.
+<c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal
+instruction</e> error message.  Likewise, if you have a Big Endian CPU and you
+try running Little Endian code on it, you'll get told <e>cannot execute binary
+file</e>.
 </p>
 
 <p>
@@ -474,7 +477,7 @@
     <b>Have you disabled packet MTU discovery and set the port range?</b><br />
     SGI boxes require <path>/proc/sys/net/ipv4/ip_no_pmtu_disc</path> = 1 and
     <path>/proc/sys/net/ipv4/ip_local_port_range</path> = "2048 32767".  See <uri
-    link="http://www.gentoo.org/doc/en/handbook/handbook-mips.xml?part=1&amp;chap=2#doc_chap4">the
+    link="/doc/en/handbook/handbook-mips.xml?part=1&amp;chap=2#doc_chap4">the
     Gentoo/MIPS handbook</uri>.
   </li>
   <li>



-- 
gentoo-doc-cvs@gentoo.org mailing list