From owner-p4-projects@FreeBSD.ORG  Sun Jun  1 23:49:33 2008
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D270E106567A; Sun,  1 Jun 2008 23:49:32 +0000 (UTC)
Delivered-To: perforce@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9390D1065676
	for <perforce@freebsd.org>; Sun,  1 Jun 2008 23:49:32 +0000 (UTC)
	(envelope-from jb@freebsd.org)
Received: from repoman.freebsd.org (repoman.freebsd.org
	[IPv6:2001:4f8:fff6::29])
	by mx1.freebsd.org (Postfix) with ESMTP id 70E218FC16
	for <perforce@freebsd.org>; Sun,  1 Jun 2008 23:49:32 +0000 (UTC)
	(envelope-from jb@freebsd.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.14.1/8.14.1) with ESMTP id m51NnWMC026066
	for <perforce@freebsd.org>; Sun, 1 Jun 2008 23:49:32 GMT
	(envelope-from jb@freebsd.org)
Received: (from perforce@localhost)
	by repoman.freebsd.org (8.14.1/8.14.1/Submit) id m51NnWNI026064
	for perforce@freebsd.org; Sun, 1 Jun 2008 23:49:32 GMT
	(envelope-from jb@freebsd.org)
Date: Sun, 1 Jun 2008 23:49:32 GMT
Message-Id: <200806012349.m51NnWNI026064@repoman.freebsd.org>
X-Authentication-Warning: repoman.freebsd.org: perforce set sender to
	jb@freebsd.org using -f
From: John Birrell <jb@FreeBSD.org>
To: Perforce Change Reviews <perforce@freebsd.org>
Cc: 
Subject: PERFORCE change 142724 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2008 23:49:33 -0000

http://perforce.freebsd.org/chv.cgi?CH=142724

Change 142724 by jb@freebsd3 on 2008/06/01 23:49:00

	IFC

Affected files ...

.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/Makefile#10 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#80 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#45 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml#20 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/cups/Makefile#1 branch
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/cups/article.sgml#1 branch
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/ldap-auth/Makefile#1 branch
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/ldap-auth/article.sgml#1 branch
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/faq/book.sgml#20 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#15 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml#12 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#16 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml#18 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#13 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#6 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml#8 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml#10 integrate
.. //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#6 integrate
.. //depot/projects/dtrace/doc/share/sgml/man-refs.ent#33 integrate
.. //depot/projects/dtrace/ports/MOVED#94 integrate
.. //depot/projects/dtrace/ports/Tools/scripts/tindex#6 integrate
.. //depot/projects/dtrace/ports/UPDATING#76 integrate
.. //depot/projects/dtrace/src/MAINTAINERS#16 integrate
.. //depot/projects/dtrace/src/games/fortune/datfiles/freebsd-tips#7 integrate
.. //depot/projects/dtrace/src/release/doc/en_US.ISO8859-1/readme/article.sgml#6 integrate
.. //depot/projects/dtrace/src/release/doc/en_US.ISO8859-1/relnotes/article.sgml#23 integrate
.. //depot/projects/dtrace/src/release/doc/share/sgml/release.ent#9 integrate
.. //depot/projects/dtrace/src/share/sendmail/Makefile#4 integrate
.. //depot/projects/dtrace/src/sys/amd64/amd64/pmap.c#45 integrate
.. //depot/projects/dtrace/src/sys/cddl/contrib/opensolaris/uts/common/dtrace/dtrace.c#9 integrate
.. //depot/projects/dtrace/src/sys/cddl/contrib/opensolaris/uts/common/sys/dtrace_impl.h#6 integrate
.. //depot/projects/dtrace/src/sys/dev/ath/ah_osdep.h#5 integrate
.. //depot/projects/dtrace/src/sys/dev/atkbdc/psm.c#10 integrate
.. //depot/projects/dtrace/src/sys/dev/nve/if_nve.c#8 integrate
.. //depot/projects/dtrace/src/sys/dev/nve/if_nvereg.h#5 integrate
.. //depot/projects/dtrace/src/sys/dev/pccard/pccard_cis.c#6 integrate
.. //depot/projects/dtrace/src/sys/fs/devfs/devfs_vnops.c#21 integrate
.. //depot/projects/dtrace/src/sys/modules/dtrace/Makefile#32 integrate
.. //depot/projects/dtrace/src/sys/netgraph/ng_nat.c#10 integrate
.. //depot/projects/dtrace/src/sys/netinet/ip_fw_nat.c#2 integrate
.. //depot/projects/dtrace/src/sys/netinet/libalias/alias.c#10 integrate
.. //depot/projects/dtrace/src/sys/netinet/libalias/alias_db.c#8 integrate
.. //depot/projects/dtrace/src/sys/netinet/libalias/alias_local.h#7 integrate
.. //depot/projects/dtrace/src/usr.sbin/bsnmpd/modules/snmp_pf/pf_snmp.c#5 integrate
.. //depot/projects/dtrace/src/usr.sbin/sicontrol/sicontrol.c#4 integrate
.. //depot/projects/dtrace/www/en/docs/books.sgml#18 integrate
.. //depot/projects/dtrace/www/en/news/news.sgml#8 integrate
.. //depot/projects/dtrace/www/en/platforms/arm.sgml#6 integrate
.. //depot/projects/dtrace/www/en/platforms/mips.sgml#4 integrate
.. //depot/projects/dtrace/www/en/security/security.sgml#14 integrate

Differences ...

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/Makefile#10 (text+ko) ====

@@ -1,4 +1,4 @@
-# $FreeBSD: doc/en_US.ISO8859-1/articles/Makefile,v 1.58 2008/04/28 15:44:35 gabor Exp $
+# $FreeBSD: doc/en_US.ISO8859-1/articles/Makefile,v 1.60 2008/05/31 13:32:19 remko Exp $
 
 SUBDIR =
 SUBDIR+= 5-roadmap
@@ -12,6 +12,7 @@
 SUBDIR+= contributing
 SUBDIR+= contributing-ports
 SUBDIR+= contributors
+SUBDIR+= cups
 SUBDIR+= cvs-freebsd
 SUBDIR+= cvsup-advanced
 SUBDIR+= dialup-firewall
@@ -29,6 +30,7 @@
 SUBDIR+= hubs
 SUBDIR+= ipsec-must
 SUBDIR+= laptop
+SUBDIR+= ldap-auth
 SUBDIR+= linux-comparison
 SUBDIR+= linux-emulation
 SUBDIR+= linux-users

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#80 (text+ko) ====

@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.801 2008/05/31 04:24:41 lippe Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.803 2008/06/01 00:14:49 miwi Exp $ -->
 <!--
 	NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical
 	order by first name.
@@ -1500,7 +1500,7 @@
       <para>Chess Griffin
 	<email>chess@chessgriffin.com</email></para>
     </listitem>
-    
+
     <listitem>
       <para>Chet Ramey
 	<email>chet@odin.INS.CWRU.Edu</email></para>
@@ -10017,6 +10017,11 @@
     </listitem>
 
     <listitem>
+      <para>Yi-Jheng Lin
+	<email>yzlin@cs.nctu.edu.tw</email></para>
+    </listitem>
+
+    <listitem>
       <para>Ying-Chieh Chen
 	<email>yinjieh@csie.nctu.edu.tw</email></para>
     </listitem>

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#45 (text+ko) ====

@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.227 2008/05/24 08:41:30 manolis Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.228 2008/06/01 00:14:49 miwi Exp $ -->
 <!--
 	NOTE TO NEW COMMITTERS: Core and committers lists are sorted in
 	alphabetical order by last name. Please keep in mind that fact while
@@ -588,7 +588,7 @@
 
     <listitem>
       <para>&a.manolis;</para>
-    </listitem> 
+    </listitem>
 
     <listitem>
       <para>&a.kientzle;</para>

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml#20 (text+ko) ====

@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml,v 1.52 2007/10/14 11:55:29 joel Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml,v 1.53 2008/06/01 00:14:49 miwi Exp $ -->
 
   <itemizedlist>
     <listitem>
@@ -324,7 +324,7 @@
         <ulink url="http://freebsd.kde.org/memoriam/alane.php">2003</ulink>)
       </para>
     </listitem>
-    
+
     <listitem>
       <para>&a.amurai; (1995 - 2003)</para>
     </listitem>
@@ -705,8 +705,8 @@
       <para>Andrew L. Moore (1993 - 1995)</para>
     </listitem>
   </itemizedlist>
-  
-<!-- 
+
+<!--
   Local Variables:
   mode: sgml
   sgml-declaration: "chapter.decl"

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/faq/book.sgml#20 (text+ko) ====

@@ -10,7 +10,7 @@
 
     <corpauthor>The FreeBSD Documentation Project</corpauthor>
 
-    <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.827 2008/05/27 23:51:07 gabor Exp $</pubdate>
+    <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.851 2008/06/01 19:44:27 pgj Exp $</pubdate>
 
     <copyright>
       <year>1995</year>
@@ -2029,8 +2029,8 @@
         <answer>
           <para>Because your world and kernel are out of sync.  This
             is not supported.  Be sure you use <command>make
-            buildworld</command> and <command>make
-            buildkernel</command> to update your kernel.</para>
+            <maketarget>buildworld</maketarget></command> and <command>make
+            <maketarget>buildkernel</maketarget></command> to update your kernel.</para>
 
 	  <para>You can boot by specifying the kernel directly at the
             second stage, pressing any key when the | shows up before
@@ -2951,7 +2951,7 @@
         <answer>
           <para>This is usually caused by an interrupt conflict (e.g.,
             two boards using the same IRQ).  Boot with the
-            -c option and change the ed0/de0/... entry to match your
+            <option>-c</option> option and change the ed0/de0/... entry to match your
             board.</para>
 
           <para>If you are using the BNC connector on your network card,
@@ -3029,18 +3029,18 @@
             that the compiler is carrying out changes each
             time.</para>
 
-          <para>For example, suppose you are running <quote>make
-            buildworld</quote>, and the compile fails while trying to
+          <para>For example, suppose you are running <command>make
+            <maketarget>buildworld</maketarget></command>, and the compile fails while trying to
             compile <filename>ls.c</filename> into
-            <filename>ls.o</filename>. If you then run <quote>make
-            buildworld</quote> again, and the compile fails in the same
-            place then this is a broken build -- try updating your sources
+            <filename>ls.o</filename>. If you then run <command>make
+            <maketarget>buildworld</maketarget></command> again, and the compile fails in the same
+            place then this is a broken build &mdash; try updating your sources
             and try again. If the compile fails elsewhere then this is
             almost certainly hardware.</para>
 
           <para>What you should do:</para>
 
-          <para>In the first case you can use a debugger e.g. gdb to find
+          <para>In the first case you can use a debugger e.g. &man.gdb.1; to find
             the point in the program which is attempting to access a bogus
             address and then fix it.</para>
 
@@ -3152,7 +3152,7 @@
               Due to a bug (feature?) in the &man.sio.4;
               driver it will touch this port even if you do not have the
               fourth serial port, and <emphasis>even</emphasis> if
-              you disable sio3 (the fourth port) which normally uses this
+              you disable <devicename>sio3</devicename> (the fourth port) which normally uses this
               address.</para>
 
             <para>Until the bug has been fixed, you can use this
@@ -3169,7 +3169,7 @@
                     <devicename>sio1</devicename>,
                     <devicename>sio2</devicename> and
                     <devicename>sio3</devicename> (all of them).  This way
-                    the sio driver does not get activated -&gt; no
+                    the &man.sio.4; driver does not get activated &mdash; no
                     problems.</para>
                 </listitem>
 
@@ -3180,7 +3180,7 @@
 
           <para>If you want to be able to use your serial ports, you will
             have to build a new kernel with the following modification: in
-            <filename>/usr/src/sys/i386/isa/sio.c</filename> find the one
+            <filename>/usr/src/sys/dev/sio.c</filename> (or in <filename>/usr/src/sys/pc98/cbus/sio.c</filename> for pc98) find the one
             occurrence of the string <literal>0x2e8</literal> and remove
             that string and the preceding comma (keep the trailing comma).
             Now follow the normal procedure of building a new
@@ -3216,7 +3216,7 @@
             get the full memory information...but for now we are stuck with
             the kernel option.</para>
 
-          <para><literal>options "MAXMEM=<replaceable>n</replaceable>"</literal></para>
+          <programlisting>options MAXMEM=<replaceable>n</replaceable></programlisting>
 
           <para>Where <replaceable>n</replaceable> is your memory in
             Kilobytes. For a 128 MB machine, you would want to use
@@ -3227,7 +3227,7 @@
       <qandaentry>
 	<question id="kmem-map-too-small">
 	  <para>My system has more than 1 GB of RAM, and I'm getting panics
-	    with <quote>kmem_map too small</quote> messages. What is wrong?
+	    with <errorname>kmem_map too small</errorname> messages. What is wrong?
 	    </para>
 	</question>
 
@@ -3255,7 +3255,7 @@
       <qandaentry>
 	<question id="panic-kmemmap-too-small">
 	  <para>My system does not have 1 GB of RAM, and FreeBSD still
-	    panics with <errorname>kmem_map too small!</errorname>
+	    panics with <errorname>kmem_map too small</errorname>!
 	    </para>
 	</question>
 
@@ -3379,41 +3379,14 @@
       <qandaentry>
         <question id="mail-loopback">
           <para>Why does Sendmail give me an error reading
-            <quote><errorname>mail loops back to
-              myself</errorname></quote>?</para>
+            <errorname>mail loops back to
+              myself</errorname>?</para>
         </question>
 
         <answer>
-          <para>This is answered in the sendmail FAQ as follows:</para>
-
-<literallayout>        * I'm getting "Local configuration error" messages, such as:
-
-        553 relay.domain.net config error: mail loops back to myself
-        554 &lt;user@domain.net&gt;... Local configuration error
-
-        How can I solve this problem?
-
-        You have asked mail to the domain (e.g., domain.net) to be
-        forwarded to a specific host (in this case, relay.domain.net)
-        by using an MX record, but the relay machine does not recognize
-        itself as domain.net.  Add domain.net to /etc/mail/local-host-names
-        (if you are using FEATURE(use_cw_file)) or add "Cw domain.net"
-        to /etc/mail/sendmail.cf.
-            </literallayout>
-
-          <para>The current version of the <ulink
-            url="ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/sendmail-faq">sendmail
-            FAQ</ulink> is no longer maintained with the sendmail release.
-            It is however regularly posted to <ulink
-            url="news:comp.mail.sendmail">comp.mail.sendmail</ulink>,
-            <ulink url="news:comp.mail.misc">comp.mail.misc</ulink>, <ulink
-            url="news:comp.mail.smail">comp.mail.smail</ulink>, <ulink
-            url="news:comp.answers">comp.answers</ulink>, and <ulink
-            url="news:news.answers">news.answers</ulink>. You can also
-            receive a copy via email by sending a message to
-            <email>mail-server@rtfm.mit.edu</email> with the command
-            <literal>send usenet/news.answers/mail/sendmail-faq</literal>
-            as the body of the message.</para>
+          <para>You can find a detailed answer for this question
+            in the <ulink
+             url="&url.books.handbook;/mail-trouble.html#Q26.5.2.">Handbook</ulink>.</para>
         </answer>
       </qandaentry>
 
@@ -3433,7 +3406,7 @@
             <itemizedlist>
               <listitem>
                 <para>After logging on to the remote machine, set your
-                  TERM shell variable to <literal>ansi</literal> or
+                  <envar>TERM</envar> shell variable to <literal>ansi</literal> or
                   <literal>sco</literal> if the remote machine knows
                   about these terminal types.</para>
               </listitem>
@@ -3445,7 +3418,7 @@
                   to run multiple concurrent sessions from one terminal,
                   and is a neat program in its own right. Each
                   <application>screen</application> window behaves like a
-                  VT100 terminal, so the TERM variable at the remote end
+                  VT100 terminal, so the <envar>TERM</envar> variable at the remote end
                   should be set to <literal>vt100</literal>.</para>
               </listitem>
 
@@ -3461,7 +3434,7 @@
                 <para>Fire up an X server at the FreeBSD end and login to
                   the remote machine using an X based terminal emulator
                   such as <command>xterm</command> or
-                  <command>rxvt</command>. The TERM variable at the remote
+                  <command>rxvt</command>. The <envar>TERM</envar> variable at the remote
                   host should be set to <literal>xterm</literal> or
                   <literal>vt100</literal>.</para>
               </listitem>
@@ -3485,7 +3458,7 @@
             first.</para>
 
           <para>A side effect of this problem are dying processes with the
-            message <quote>SIGXCPU exceeded cpu time limit</quote>.</para>
+            message <errorname>SIGXCPU exceeded cpu time limit</errorname>.</para>
 
           <para>If the problem cannot be fixed otherwise the solution
             is to set this sysctl variable:</para>
@@ -3527,7 +3500,7 @@
             Wemm, in answer to a question about an internal modem that was
             no longer found after an upgrade to FreeBSD 4.X (the comments
             in <literal>[]</literal> have been added to clarify the
-            context.</para>
+            context).</para>
 
           <note>
             <para>The contents of this quotation has been updated from
@@ -3635,7 +3608,7 @@
           <para>Add the hexadecimal Vendor ID for your device in the
             correct place, save the file, rebuild your kernel, and reboot.
             Your device should now be found as an <literal>sio</literal>
-            device as it was under FreeBSD 3.X</para>
+            device as it was under FreeBSD 3.X.</para>
         </answer>
       </qandaentry>
 
@@ -3665,7 +3638,7 @@
 
             <listitem>
               <para>You are not using <command>/boot/loader</command> to load
-                your kernel, but doing it directly from boot2 (see
+                your kernel, but doing it directly from <filename>boot2</filename> (see
                 &man.boot.8;).  While there is nothing wrong with bypassing
                 <command>/boot/loader</command>, it generally does a better
                 job of making the kernel symbols available to user
@@ -3689,7 +3662,8 @@
 
           <para>The problem: more likely than not, the delay is caused by
             the server software trying to resolve the client's IP address
-            into a hostname.  Many servers, including the Telnet and SSH
+            into a hostname.  Many servers, including the
+            <application>Telnet</application> and <application>SSH</application>
             servers that come with FreeBSD, do this in order to, among
             other things, store the hostname in a log file for future
             reference by the administrator.</para>
@@ -3713,7 +3687,7 @@
             the &man.hosts.5; and &man.named.8; manual pages for more
             information.  If this is on the global Internet, the problem
             may be that your server's resolver is not functioning
-            correctly.  To check, try to look up another host--say,
+            correctly.  To check, try to look up another host &mdash; say,
             <hostid>www.yahoo.com</hostid>.  If it does not work, that is
             your problem.</para>
 
@@ -3721,12 +3695,12 @@
 	    that domain and nameserver information is missing from
 	    <filename>/etc/resolv.conf</filename>.  This will often cause
 	    a delay in <application>SSH</application>, as the option
-	    <quote>UseDNS</quote> is set to <quote>yes</quote> by default
+	    <literal>UseDNS</literal> is set to <literal>yes</literal> by default
 	    in the <filename>sshd_config</filename> file in
 	    <filename>/etc/ssh</filename>.  If this is causing the
 	    problem, you will either need to fill in the missing information
-	    in <filename>/etc/resolv.conf</filename> or set <quote>UseDNS</quote>
-	    to <quote>no</quote> in <filename>sshd_config</filename>
+	    in <filename>/etc/resolv.conf</filename> or set <literal>UseDNS</literal>
+	    to <literal>no</literal> in <filename>sshd_config</filename>
 	    as a temporary workaround.</para>
 	</answer>
       </qandaentry>
@@ -3837,7 +3811,7 @@
 	  <para>This problem is common on laptops that boot more than
 	    one operating system.  Some non-BSD operating systems
 	    leave PC card hardware in an inconsistent state.
-	    <command>pccardd</command> will detect the card as
+	    &man.pccardd.8; will detect the card as
 	    <errorname>"(null)""(null)"</errorname> instead of its
 	    actual model.</para>
 
@@ -3862,7 +3836,7 @@
 
         <answer>
           <para>FreeBSD's boot loader is incorrectly recognizing the hard 
-            drive's geometry. This must be manually set within fdisk when 
+            drive's geometry. This must be manually set within &man.fdisk.8; when
             creating or modifying FreeBSD's slice.
           </para>
 
@@ -3881,7 +3855,7 @@
             <userinput>5000/250/60</userinput>.
           </para>
 
-          <para>Press enter to set the values, and hit
+          <para>Press <keycap>Enter</keycap> to set the values, and hit
             <keycap>W</keycap> to write the new partition table to the
             drive.</para>
         </answer>
@@ -3894,9 +3868,9 @@
         </question>
 
         <answer>
-          <para>Enter &man.sysinstall.8; and choose Configure,
-            then Fdisk.  Select the disk the Boot Manager resided on
-            with the <keycap>space</keycap> key.  Press 
+          <para>Enter &man.sysinstall.8; and choose <guimenuitem>Configure</guimenuitem>,
+            then <guimenuitem>Fdisk</guimenuitem>.  Select the disk the Boot Manager resided on
+            with the <keycap>Space</keycap> key.  Press 
             <keycap>W</keycap> to write changes to the drive.  A prompt
             will appear asking which boot loader to install.  Select this,
             and it will be restored.
@@ -3964,48 +3938,9 @@
         </question>
 
         <answer>
-          <para>&a.rwatson; answered this question very succinctly on
-            the freebsd-current list in a thread entitled <quote><ulink
-            url="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=65165+0+/usr/local/www/db/text/2003/freebsd-current/20031221.freebsd-current">lock
-            order reversals - what do they mean?</ulink></quote></para>
-
-          <blockquote>
-            <attribution>&a.rwatson; on freebsd-current, December 14,
-              2003</attribution>
-
-            <para>These warnings are generated by Witness, a run-time lock
-              diagnostic system found in FreeBSD -CURRENT kernels (but
-              removed in releases).  You can read more about Witness in the
-              &man.witness.4; man page, which talks about its capabilities.  Among
-              other things, Witness performs run-time lock order verification
-              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 is worth
-              observing that Witness is actually slightly conservative, and so
-              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
-              spurious reports.  The non-well-known ones typically correspond
-              to bugs in newly added locking, as lock order reversals usually
-              get fixed pretty quickly because Witness is busy generating
-              warnings :-).</para>
-          </blockquote>
-
-          <note>
-	    <para>A so-called "false positive" is actually Witness tripping
-                over a much more serious bug.  Such bugs are typically a page
-                fault or memory corruption experienced inside of the kernel, or
-                a name clash with mutexes.</para>
-	  </note>
-          <note>
-            <para>See <ulink
-              url="http://sources.zabbadoz.net/freebsd/lor.html">Bjoern
-              Zeeb's lock order reversal page</ulink> for the status of
-              known lock order reversals.</para>
-          </note>
+          <para>An answer for this question can be found in the FreeBSD
+            Glosssary, see <ulink
+              url="&url.books.handbook;/freebsd-glossary.html#LOR-GLOSSARY">LOR</ulink>.</para>
         </answer>
       </qandaentry>
 
@@ -4029,7 +3964,7 @@
               block for an extended period while holding a mutex.</para>
 
           <para>To catch such errors, assertions may be added to the kernel
-              that interact with the witness subsystem to emit a warning
+              that interact with the &man.witness.4; subsystem to emit a warning
               or fatal error (depending on the system configuration) when
               a potentially blocking call is made while holding a mutex.</para>
 
@@ -4042,7 +3977,7 @@
 
       <qandaentry>
         <question id="touch-not-found">
-	  <para>Why does buildworld/installworld die with the message
+	  <para>Why does <maketarget>buildworld</maketarget>/<maketarget>installworld</maketarget> die with the message
 	    <errorname>touch: not found</errorname>?</para>
         </question>
 
@@ -4080,11 +4015,11 @@
         </question>
 
         <answer>
-	  <para>The open-source <ulink
-	    url="http://www.openoffice.org">OpenOffice.org</ulink> office
+	  <para>The open-source <application><ulink
+	      url="http://www.openoffice.org">OpenOffice.org</ulink></application> office
 	    suite works natively on FreeBSD.  The &linux; version of
-	    <ulink
-	    url="http://www.sun.com/staroffice/">StarOffice</ulink>,
+	    <application><ulink
+	      url="http://www.sun.com/staroffice/">StarOffice</ulink></application>,
 	    the value-added closed-source version of OpenOffice.org, also
 	    works on FreeBSD.</para>
 
@@ -5052,7 +4987,7 @@
           <para><anchor id="dedicate">The installation procedure allows
             you to chose two different methods in partitioning your
             hard disk(s). The default way makes it compatible with other
-            operating systems on the same machine, by using fdisk table
+            operating systems on the same machine, by using &man.fdisk.8; table
             entries (called <quote>slices</quote> in FreeBSD), with a
             FreeBSD slice that employs partitions of its own. Optionally,
             one can chose to install a boot-selector to switch between the
@@ -5062,7 +4997,7 @@
 
           <para>So why it is called <quote>dangerous</quote>?  A disk
             in this mode does not contain what normal PC utilities
-            would consider a valid fdisk table. Depending on how well
+            would consider a valid &man.fdisk.8; table. Depending on how well
             they have been designed, they might complain at you once
             they are getting in contact with such a disk, or even
             worse, they might damage the BSD bootstrap without even
@@ -6217,11 +6152,11 @@
       <qandaentry>
         <question id="sendmail-alternative">
           <para>What other mail-server software can I use instead of
-            Sendmail?</para>
+            <application>sendmail</application>?</para>
         </question>
 
         <answer>
-          <para><ulink url="http://www.sendmail.org/">Sendmail</ulink> is
+          <para><ulink url="http://www.sendmail.org/"><application>Sendmail</application></ulink> is
             the default mail-server software for FreeBSD, but you can
             easily replace it with one of the other MTA (for instance,
             an MTA installed from the ports).</para>
@@ -6237,7 +6172,7 @@
           <para>Diversity is nice, and the fact that you have many
             different mail-servers to chose from is considered a
             good thing; therefore try to avoid
-            asking questions like <quote>Is Sendmail better than
+            asking questions like <quote>Is <application>sendmail</application> better than
             Qmail?</quote> in the mailing lists.  If you do feel like
             asking, first check the mailing list archives.  The
             advantages and disadvantages of each and every one of the
@@ -8528,12 +8463,12 @@
 
       <qandaentry>
         <question id="sendmail-port-587">
-          <para>Sendmail is listening on port 587 as well as the
+          <para><application>sendmail</application> is listening on port 587 as well as the
             standard port 25! What is going on?</para>
         </question>
 
         <answer>
-          <para>Recent versions of Sendmail support a
+          <para>Recent versions of <application>sendmail</application> support a
             mail submission feature that runs over port 587.  This is
             not yet widely supported, but is growing in
             popularity.</para>
@@ -8902,7 +8837,7 @@
             make install</command>.  When &man.ppp.8; hangs, find the
             &man.ppp.8; process id with <command>ps ajxww | fgrep
             ppp</command> and run <command>gdb ppp
-            <replaceable>PID</replaceable></command>.  From the gdb
+            <replaceable>PID</replaceable></command>.  From the <command>gdb</command>
             prompt, you can then use <command>bt</command> to get a
             stack trace.</para>
 
@@ -9156,7 +9091,7 @@
           <para>In the DNS case, you should try to determine what is
             actually trying to resolve a host name.  A lot of the
             time, &man.sendmail.8; is the culprit.  You should make
-            sure that you tell sendmail not to do any DNS lookups in
+            sure that you tell <application>sendmail</application> not to do any DNS lookups in
             its configuration file.  See the section on <ulink
             url="&url.books.handbook;/smtp-dialup.html">using email with a
             dialup connection</ulink> in the FreeBSD Handbook for
@@ -9167,7 +9102,7 @@
 
           <programlisting>define(`confDELIVERY_MODE', `d')dnl</programlisting>
 
-          <para>This will make sendmail queue everything until the
+          <para>This will make <application>sendmail</application> queue everything until the
             queue is run (usually, sendmail is invoked with
             <option>-bd -q30m</option>, telling it to run the queue
             every 30 minutes) or until a <command>sendmail
@@ -9331,7 +9266,7 @@
           <para>All of this information should be given alongside your
             question, making it possible to diagnose the problem.</para>
 
-          <para>If you are familiar with gdb, you may wish to find out some
+          <para>If you are familiar with &man.gdb.1;, you may wish to find out some
             other bits and pieces such as what actually caused the dump and
             the addresses &amp; values of the relevant variables.</para>
         </answer>
@@ -9748,7 +9683,7 @@
             using port address <literal>0x3f8</literal>, and has a
             16550A-type UART chip.  The second uses the same kind of chip
             but is on irq 3 and is at port address <literal>0x2f8</literal>.
-            Internal modem cards are treated just like serial ports---except
+            Internal modem cards are treated just like serial ports &mdash; except
             that they always have a modem <quote>attached</quote> to the
             port.</para>
 
@@ -9956,7 +9891,7 @@
             The terminal type for this port is
             <literal>dialup</literal>.  The port is
             <literal>on</literal> and is
-            <literal>insecure</literal>---meaning
+            <literal>insecure</literal> &mdash; meaning
             <username>root</username> logins on the port are not
             allowed. For dialin ports like this one, use the
             <devicename>ttyd<replaceable>X</replaceable></devicename>
@@ -10049,7 +9984,7 @@
 
       <qandaentry>
         <question id="hayes-unsupported">
-          <para>My stock Hayes modem is not supported---what
+          <para>My stock Hayes modem is not supported &mdash; what
             can I do?</para>
         </question>
 
@@ -10061,7 +9996,7 @@
             file.</para>
 
           <para>The Hayes driver is not smart enough to recognize some of
-            the advanced features of newer modems---messages like
+            the advanced features of newer modems &mdash; messages like
             <literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or
             <literal>CONNECT 115200</literal> will just confuse it. You
             should turn those messages off when you use &man.tip.1;

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#15 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.406 2008/03/04 07:11:37 brd Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.407 2008/06/01 09:42:11 remko Exp $
 -->
 
 <chapter id="advanced-networking">
@@ -2165,11 +2165,6 @@
 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3,
       wMaxPacketSize=49, nframes=6, buffer size=294</screen>
 
-      <note>
-	<para>The Bluetooth stack has to be started manually on &os; 6.0, and
-	  on &os; 5.X before 5.5.  It is done automatically from &man.devd.8;
-	  on &os; 5.5, 6.1 and newer.</para>
-
       <para>Copy
         <filename>/usr/share/examples/netgraph/bluetooth/rc.bluetooth</filename>
         into some convenient place, like <filename>/etc/rc.bluetooth</filename>.
@@ -2190,7 +2185,6 @@
 Number of ACL packets: 8
 Max. SCO packet size: 64 bytes
 Number of SCO packets: 8</screen>
-      </note>
 
     </sect2>
 
@@ -2509,12 +2503,6 @@
 
       <screen>&prompt.root; <userinput>/etc/rc.d/sdpd start</userinput></screen>
 
-      <para>On &os; 6.0, and on &os; 5.X before 5.5,
-	<application>sdpd</application> is not integrated into the system
-	startup scripts.  It has to be started manually with:</para>
-
-      <screen>&prompt.root; <userinput>sdpd</userinput></screen>
-
       <para>The local server application that wants to provide Bluetooth
         service to the remote clients will register service with the local
         SDP daemon. The example of such application is &man.rfcomm.pppd.8;.

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml#12 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.230 2008/05/19 18:32:41 remko Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.232 2008/06/01 09:42:11 remko Exp $
 -->
 
 <chapter id="config-tuning">
@@ -367,13 +367,11 @@
 
     <para>While every script must meet some minimal requirements, most
       of the time these requirements are &os; version
-      agnostic.  Each script must have a <filename>.sh</filename>
-      extension appended to the end and every script must be
-      executable by the system.  The latter may be achieved by using
-      the <command>chmod</command> command and setting the unique permissions
-      of <literal>755</literal>.  There should also be, at minimal,
-      an option to <literal>start</literal> the application and an
-      option to <literal>stop</literal> the application.</para>
+      agnostic.  Each script must be executable by the system; this is 
+      typically achieved by using the <command>chmod</command> command and 
+      setting the unique permissions of <literal>555</literal>.  There should 
+      also be, at minimal, options to <literal>start</literal> and <literal>stop</literal> 
+      the application.</para>
 
     <para>The simplest start up script would probably look a little
       bit like this one:</para>
@@ -2171,7 +2169,7 @@
           connected at once, the resources needed may be similar to a
           high-scale web server.</para>
 
-        <para>As of FreeBSD 4.5, <varname>kern.maxusers</varname> is
+        <para>The variable <varname>kern.maxusers</varname> is
           automatically sized at boot based on the amount of memory available
           in the system, and may be determined at run-time by inspecting the
           value of the read-only <varname>kern.maxusers</varname> sysctl.
@@ -2184,9 +2182,7 @@
           boot-time or run-time in <filename>/boot/loader.conf</filename> (see
           the &man.loader.conf.5; man page or the
           <filename>/boot/defaults/loader.conf</filename> file for some hints)
-          or as described elsewhere in this document.  Systems older than
-          FreeBSD&nbsp;4.4 must set this value via the kernel &man.config.8;
-          option <option>maxusers</option> instead.</para>
+          or as described elsewhere in this document.</para>
 
 	<para>In older releases, the system will auto-tune
 	  <literal>maxusers</literal> for you if you explicitly set it to
@@ -2218,14 +2214,7 @@
 	    limit the number of users which can log into your machine.  It
 	    simply sets various table sizes to reasonable values considering
 	    the maximum number of users you will likely have on your system
-	    and how many processes each of them will be running.  One keyword
-	    which <emphasis>does</emphasis> limit the number of simultaneous
-	    remote logins and X terminal windows is <link
-	    linkend="kernelconfig-ptys"><literal>pseudo-device pty
-	    16</literal></link>.  With &os;&nbsp;5.X, you do not have to
-	    worry about this number since the &man.pty.4; driver is
-	    <quote>auto-cloning</quote>; you simply use the line
-	    <literal>device pty</literal> in your configuration file.</para>
+	    and how many processes each of them will be running.</para>
 	</note>
 
       </sect3>

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#16 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml,v 1.81 2008/03/01 17:50:03 loader Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml,v 1.82 2008/06/01 09:42:11 remko Exp $
 -->
 
 <chapter id="firewalls">
@@ -393,9 +393,8 @@
       <warning>
 	<para>When browsing the pf user's guide, please keep in mind that
      different versions of &os; contain different versions of pf.  The
-     <application>pf</application> firewall in &os; 5.X is at the level
-     of OpenBSD version 3.5 and in &os; 6.X is at the level of OpenBSD
-     version 3.7.</para>
+     <application>pf</application> firewall in &os; 6.X is at the level
+     of OpenBSD version 3.7.</para>
       </warning>
 
       <para>The &a.pf; is a good place to ask questions about

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml#18 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.389 2008/04/25 19:03:56 remko Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.390 2008/06/01 08:51:29 remko Exp $
 -->
 
 <chapter id="install">
@@ -2030,15 +2030,6 @@
 	<literal>G</literal> for gigabytes, or <literal>C</literal> for
 	cylinders.</para>
 
-      <note><para>Beginning with FreeBSD&nbsp;5.X, users can: select
-	<acronym>UFS2</acronym> (which is default on &os;&nbsp;5.1 and
-	above) using the <literal>Custom Newfs</literal>
-	(<keycap>Z</keycap>) option, create labels with
-	<literal>Auto Defaults</literal> and modify them with the <literal>Custom Newfs</literal> option or
-	add <option>-O 2</option> during the regular creation period.
-	Do not forget to add <option>-U</option> for SoftUpdates if you use the <literal>Custom Newfs</literal>
-	option!</para></note>
-
       <figure id="sysinstall-label-add">
 	<title>Free Space for Root Partition</title>
 
@@ -2428,8 +2419,8 @@
       installation.    An option can be configured by re-entering the
       configuration options before booting the new FreeBSD
       system or after installation using
-      <command>sysinstall</command> (<command>/stand/sysinstall</command>
-      in &os; versions older than 5.2) and selecting
+      <command>sysinstall</command>
+      and selecting
       <guimenuitem>Configure</guimenuitem>.</para>
 
     <sect2 id="inst-network-dev">
@@ -3472,8 +3463,8 @@
 
       <para>Groups can also be added at this time if specific needs
 	are known.  Otherwise, this may be accessed through using
-	<command>sysinstall</command> (<command>/stand/sysinstall</command>
-	in &os; versions older than 5.2) after installation is
+	<command>sysinstall</command>
+	after installation is
 	completed.</para>
 
       <para>When you are finished adding users, select 
@@ -3512,9 +3503,7 @@
 
       <para>If you need to configure <link linkend="network-services">additional network services</link> or
 	any other configuration, you can do it at this point or
-	after installation with <command>sysinstall</command>
-	(<command>/stand/sysinstall</command> in &os; versions older
-	than 5.2).</para>
+	after installation with <command>sysinstall</command>.</para>
 
       <screen>                     User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
@@ -4147,7 +4136,7 @@
 	      drive is not probed.</para>
 	  </question>
 	  <answer>
-	    <para>&os; 5.0 and above makes extensive use of the system
+	    <para>&os; makes extensive use of the system
 	      ACPI service on the i386, amd64 and ia64 platforms to
 	      aid in system configuration if it is detected during
 	      boot.  Unfortunately, some bugs still exist in both the
@@ -4417,9 +4406,6 @@
 
 	    <screen>&prompt.root; <userinput>cu -l /dev/cuad0</userinput></screen>
 
-	    <para>On &os;&nbsp;5.X, use
-	      <filename>/dev/cuaa0</filename> instead of
-	      <filename>/dev/cuad0</filename>.</para>
 	  </step>
       </procedure>
 
@@ -4497,7 +4483,7 @@
 	  <para>That directory will normally contain the following images:</para>
 
 	  <table frame="none">
-	    <title>FreeBSD 5.<replaceable>X</replaceable> and 6.<replaceable>X</replaceable>
+	    <title>FreeBSD 6.<replaceable>X</replaceable> and 7.<replaceable>X</replaceable>
 	      ISO Image Names and Meanings</title>
 
 	    <tgroup cols="2">
@@ -4531,14 +4517,14 @@
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
-		  <entry>&os; documentation (prior to &os; 6.2) and as many 
+		  <entry>As many 
 		    third-party packages as would fit on the disc.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-docs.iso</filename></entry>
 
-		  <entry>&os; documentation (for &os; 6.2 and later).</entry>
+		  <entry>&os; documentation.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#13 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.183 2008/05/05 14:14:39 gabor Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.184 2008/06/01 09:42:12 remko Exp $
 -->
 
 <chapter id="kernelconfig">
@@ -975,7 +975,7 @@
 #device          apm</programlisting>
 
     <para>Advanced Power Management support.  Useful for laptops,
-      although in &os; 5.X and above this is disabled in
+      although this is disabled in
       <filename>GENERIC</filename> by default.</para>
 
     <programlisting># Add suspend/resume support for the i8254.

==== //depot/projects/dtrace/doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#6 (text+ko) ====

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.136 2007/01/26 20:47:36 pav Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.138 2008/06/01 15:50:43 remko Exp $
 -->
 
 <chapter id="mail">
@@ -702,12 +702,6 @@
     <sect2 id="mail-disable-sendmail">
       <title>Disable <application>sendmail</application></title>
 
-      <para>The procedure used to start
-	<application>sendmail</application> changed significantly
-	between 4.5-RELEASE, 4.6-RELEASE, and later releases.
-	Therefore, the procedure used to disable it is subtly
-	different.</para>
-
 	<warning>
 	  <para>If you disable <application>sendmail</application>'s
 	    outgoing mail service, it is important that you replace it
@@ -724,53 +718,10 @@
 	    never be delivered.</para>
 	</warning>
 
-      <sect3>
-	<title>FreeBSD 4.5-STABLE before 2002/4/4 and Earlier
-	  (Including 4.5-RELEASE and Earlier)</title>
-
-	<para>Enter:</para>
-
-	  <programlisting>sendmail_enable="NO"</programlisting>
-
-	  <para>into <filename>/etc/rc.conf</filename>.  This will disable
-	  <application>sendmail</application>'s incoming mail service,
-	  but if <filename>/etc/mail/mailer.conf</filename> (see below)
-	  is not changed, <application>sendmail</application> will
-	  still be used to send e-mail.</para>
-      </sect3>
-
-      <sect3>
-	<title>FreeBSD 4.5-STABLE after 2002/4/4
-	  (Including 4.6-RELEASE and Later)</title>
-
 	<para>In order to completely disable
 	  <application>sendmail</application>, including the outgoing
 	  mail service, you must use</para>
 
-	  <programlisting>sendmail_enable="NONE"</programlisting>
-
-	  <para>in <filename>/etc/rc.conf.</filename></para>
-
-	<para>If you only want to disable
-	  <application>sendmail</application>'s incoming mail service,
-	  you should set</para>
-
-	  <programlisting>sendmail_enable="NO"</programlisting>
-
-	<para>in <filename>/etc/rc.conf</filename>.  However, if
-	  incoming mail is disabled, local delivery will still
-	  function.  More information on 
-	  <application>sendmail</application>'s startup options is
-	  available from the &man.rc.sendmail.8; manual page.</para>

>>> TRUNCATED FOR MAIL (1000 lines) <<<