From jcamou@cox.net  Wed Aug 25 19:24:55 2004
Return-Path: <jcamou@cox.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D57B916A4D8
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 25 Aug 2004 19:24:55 +0000 (GMT)
Received: from fed1rmmtao03.cox.net (fed1rmmtao03.cox.net [68.230.241.36])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A722243D45
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 25 Aug 2004 19:24:55 +0000 (GMT)
	(envelope-from jcamou@cox.net)
Received: from nightfall.cox.net ([68.0.135.88]) by fed1rmmtao03.cox.net
          (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709)
          with ESMTP
          id <20040825192449.CGZZ5706.fed1rmmtao03.cox.net@nightfall.cox.net>
          for <FreeBSD-gnats-submit@freebsd.org>;
          Wed, 25 Aug 2004 15:24:49 -0400
Received: by nightfall.cox.net (Postfix, from userid 1002)
	id 94F1146; Wed, 25 Aug 2004 11:25:00 -0700 (MST)
Message-Id: <20040825182500.94F1146@nightfall.cox.net>
Date: Wed, 25 Aug 2004 11:25:00 -0700 (MST)
From: Jesus R.Camou <jcamou@cox.net>
Reply-To: Jesus R.Camou <jcamou@cox.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: [PATCH] faq updates and fixes	
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         70954
>Category:       docs
>Synopsis:       [PATCH] faq updates and fixes
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 25 19:30:32 GMT 2004
>Closed-Date:    Thu Aug 26 20:16:49 GMT 2004
>Last-Modified:  Thu Aug 26 20:16:49 GMT 2004
>Originator:     Jesus R. Camou
>Release:        FreeBSD 4.10-STABLE i386
>Organization:
>Environment:
System: FreeBSD nightfall.cox.net 4.10-STABLE FreeBSD 4.10-STABLE #11: Mon Jul 26 20:10:25 MST 2004 root@nightfall.cox.net:/usr/obj/usr/src/sys/NIGHTFALL i386


>Description:

	o Add Italian (it_IT.ISO8859-15) to the list of languages and
	encodings.

	o Remove quite a few contractions.

	o Add <hostid> tags for cvsup.FreeBSD.org

>How-To-Repeat:

>Fix:

	

--- faq.en.diff begins here ---
Index: book.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.641
diff -u -r1.641 book.sgml
--- book.sgml	16 Aug 2004 01:05:20 -0000	1.641
+++ book.sgml	25 Aug 2004 19:14:04 -0000
@@ -759,6 +759,12 @@
                       <entry>French</entry>
                     </row>
 
+		    <row>
+		      <entry><literal>it_IT.ISO8859-15</literal></entry>
+
+		      <entry>Italian</entry>
+		    </row>
+
                     <row>
                       <entry><literal>ja_JP.eucJP</literal></entry>
 
@@ -4296,7 +4302,7 @@
 
 	  <para>You must remove all power from the PC card slot to
 	    fully reset the hardware.  Completely power off the
-	    laptop.  (Don't suspend it, don't let it go into standby;
+	    laptop.  (Do not suspend it, do not let it go into standby;
 	    the power needs to be completely off.)  Wait a few
 	    moments, and reboot.  Your PC card should work now.</para>
 
@@ -4396,7 +4402,7 @@
           <para>The problem can be caused by many factors, although
             perhaps the most common cause is faulty or incorrect
             cabling.  Check that the ATA cables are undamaged and rated
-            for the Ultra DMA mode in use.  If you're using removable
+            for the Ultra DMA mode in use.  If you are using removable
             drive trays, they must also be compatible.  Be sure that
             all connections are making good contact.  Problems have
             also been noticed when an old drive is installed on the
@@ -4438,10 +4444,10 @@
               using a combination of hard coded lock orders, and run-time
               detected lock orders, and generates console warnings when lock
               orders are violated.  The intent of this is to detect the
-              potential for deadlocks due to lock order violations; it's worth
+              potential for deadlocks due to lock order violations; it is worth
               observing that Witness is actually slightly conservative, and so
-              it's possible to get false positives.  In the event that Witness
-              is accurately reporting a lock order problem, it's basically
+              it is possible to get false positives.  In the event that Witness
+              is accurately reporting a lock order problem, it is basically
               saying "If you were unlucky, a deadlock would have happened
               here".  There are a couple of "well known" false positives,
               which we need to do a better job of documenting to prevent
@@ -6334,7 +6340,7 @@
 	    <username>root</username> user.
 	    &man.df.1; does not count that space when
 	    calculating the <literal>Capacity</literal> column, so it can
-	    exceed 100%.  Also, you'll notice that the
+	    exceed 100%.  Also, you will notice that the
 	    <literal>Blocks</literal> column is always greater than the
 	    sum of the <literal>Used</literal> and
 	    <literal>Avail</literal> columns, usually by a factor of
@@ -8358,7 +8364,7 @@
             just a special case of the previous question and works
             perfectly well.</para>
 
-	  <para>If you're using dialup to connect to the Internet
+	  <para>If you are using dialup to connect to the Internet
             user-mode &man.ppp.8; contains a <option>-nat</option>
             option. If you run &man.ppp.8; with the
             <option>-nat</option> option, set
@@ -8439,7 +8445,7 @@
         </question>
 
         <answer>
-          <para>Because they aren't necessary. In the Berkeley
+          <para>Because they are not necessary. In the Berkeley
             networking framework, network interfaces are only directly
             accessible by kernel code. Please see the
             <filename>/etc/rc.network</filename> file and the manual
@@ -11897,7 +11903,7 @@
 	    server hourly, this update might happen at any time during
 	    the hour.  This means that some servers have newer code
 	    than others, even though all servers have code that is
-	    less than an hour old.  If cvsup.FreeBSD.org was a round
+	    less than an hour old.  If <hostid>cvsup.FreeBSD.org</hostid> was a round
 	    robin DNS entry that simply redirected users to a random
 	    CVSup server, running CVSup twice in a row could download
 	    code older than the code already on the system.</para>
--- faq.en.diff ends here ---


>Release-Note:
>Audit-Trail:

From: Marc Fonvieille <blackend@FreeBSD.org>
To: "Jesus R.Camou" <jcamou@cox.net>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: docs/70954: [PATCH] faq updates and fixes
Date: Wed, 25 Aug 2004 21:47:21 +0200

 On Wed, Aug 25, 2004 at 11:25:00AM -0700, Jesus R.Camou wrote:
 [...]
 > @@ -11897,7 +11903,7 @@
 >  	    server hourly, this update might happen at any time during
 >  	    the hour.  This means that some servers have newer code
 >  	    than others, even though all servers have code that is
 > -	    less than an hour old.  If cvsup.FreeBSD.org was a round
 > +	    less than an hour old.  If <hostid>cvsup.FreeBSD.org</hostid> was a round
 
 
 				 <hostid role="fqdn">cvsup.FreeBSD.org</hostid>
 
 
 >  	    robin DNS entry that simply redirected users to a random
 >  	    CVSup server, running CVSup twice in a row could download
 >  	    code older than the code already on the system.</para>
 > --- faq.en.diff ends here ---
 > 
 
 Marc
State-Changed-From-To: open->closed 
State-Changed-By: ceri 
State-Changed-When: Thu Aug 26 20:16:32 GMT 2004 
State-Changed-Why:  
Committed in two parts; thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=70954 
>Unformatted:
