From: "swift" <swift@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-mips-faq.xml
Date: Tue, 9 Aug 2005 11:29:38 +0000 [thread overview]
Message-ID: <200508091129.j79BTKI3028440@robin.gentoo.org> (raw)
swift 05/08/09 11:29:38
Modified: xml/htdocs/doc/en/draft gentoo-mips-faq.xml
Log:
Spell checker run
Revision Changes Path
1.3 +9 -9 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.3&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.3&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.2&r2=1.3&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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- gentoo-mips-faq.xml 9 Aug 2005 11:24:51 -0000 1.2
+++ gentoo-mips-faq.xml 9 Aug 2005 11:29:38 -0000 1.3
@@ -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.2 2005/08/09 11:24:51 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/gentoo-mips-faq.xml,v 1.3 2005/08/09 11:29:38 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/draft/gentoo-mips-faq.xml">
@@ -53,7 +53,7 @@
<p>
Gentoo/MIPS is a small project within the Gentoo Foundation, responsible for
looking after the MIPS port of Gentoo Linux. We currently look after two main
-subarchitectures of the MIPS family specifically: Silicon Graphics systems and
+sub architectures of the MIPS family specifically: Silicon Graphics systems and
MIPS-based Cobalt servers.
</p>
@@ -67,7 +67,7 @@
Okay, sure, some MIPS machines aren't the fastest boxes on the block these days.
However, despite the age of some of these beasts, they still can make very
functional, useful machines. A Cobalt Qube 2 could make a very nice broadband
-internet router, capable of hosting websites, email, IRC and numerous other
+Internet router, capable of hosting websites, email, IRC and numerous other
tasks. There are a number of reasons why you'd want to install Linux on this
sort of hardware.
</p>
@@ -137,7 +137,7 @@
<body>
<p>
-Good quesion. In short... Heaps. MIPS Processors see use inside all sorts
+Good question. In short... Heaps. MIPS Processors see use inside all sorts
of machines, ranging from small PDAs (such as the early Windows CE powered Casio
PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to
workstations such as the Silicon Graphics Indy and O2 and even high end servers
@@ -275,7 +275,7 @@
theoretically run Gentoo/MIPS. I've 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
-gauge how well Gentoo/MIPS runs on a particular machine.
+measure how well Gentoo/MIPS runs on a particular machine.
</p>
<p>
@@ -347,7 +347,7 @@
<p>
Sometimes the filename will have <c>n32</c> or <c>n64</c> in the filename as
well. These refer to 64-bit userland images. At the moment, support for 64-bit
-userlands is still quite flakey and a lot of packages are broken. I'd suggest
+userlands is still quite flaky and a lot of packages are broken. I'd suggest
leaving these alone unless you're particularly brave and don't mind a rather
bumpy ride.
</p>
@@ -454,7 +454,7 @@
<body>
<p>
-Unfortunately, not all graphics framebuffers are supported under Linux yet.
+Unfortunately, not all graphics frame buffers are supported under Linux yet.
This doesn't mean you can't use the machine... it just means you'll need a
null-modem serial cable to interact with it. It is quite possible that the
machine is in fact running, however, the system is outputting to the serial
@@ -494,7 +494,7 @@
</li>
<li>
<b>Is the server giving out the correct details via BOOTP?</b><br />
- Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISC's dhcpd won't dish
+ Double check your <path>/etc/dhcp/dhcpd.conf</path>. ISCs dhcpd won't dish
out addressing information via BOOTP unless the machine has been statically
defined with a fixed address.
</li>
@@ -502,7 +502,7 @@
<b>Are you exporting <path>/nfsroot</path> in your
<path>/etc/exports</path>?</b><br />
Make sure you are exporting that to the Cobalt machine. It only needs
- readonly access. Also remember to run <c>exportfs -av</c> after you edit
+ read-only access. Also remember to run <c>exportfs -av</c> after you edit
the file.
</li>
<li>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-08-09 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 11:29 swift [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 19:47 [gentoo-doc-cvs] cvs commit: gentoo-mips-faq.xml Sven Vermeulen
2005-09-08 12:18 Jose Luis Rivero
2005-09-06 18:00 swift
2005-09-06 17:59 swift
2005-08-30 19:04 swift
2005-08-09 13:55 swift
2005-08-09 11:24 swift
2005-08-09 11:08 swift
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=200508091129.j79BTKI3028440@robin.gentoo.org \
--to=swift@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