[svnbook] r4084 committed - Read-thru edits....

[svnbook at googlecode.com]

Revision: 4084
Author:   cmpilato at gmail.com
Date:     Fri Sep  9 06:53:11 2011
Log:      Read-thru edits.

* en/book/ch06-server-configuration.xml
   Update output from 'svnserve -i'.  Move some URLs out of the main
   text and into footnotes.  Lose a block of not-quite-right text.

http://code.google.com/p/svnbook/source/detail?r=4084

Modified:
  /trunk/en/book/ch06-server-configuration.xml

=======================================
--- /trunk/en/book/ch06-server-configuration.xml	Tue Aug 30 12:15:55 2011
+++ /trunk/en/book/ch06-server-configuration.xml	Fri Sep  9 06:53:11 2011
@@ -551,7 +551,8 @@
          <informalexample>
            <screen>
  $ svnserve -i
-( success ( 1 2 ( ANONYMOUS ) ( edit-pipeline ) ) )
+( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries  
commit-revprops d\
+epth log-revprops atomic-revprops partial-replay ) ) )
  </screen>
          </informalexample>

@@ -1585,17 +1586,17 @@
      <para>The Apache HTTP Server is a <quote>heavy-duty</quote>
        network server that Subversion can leverage.  Via a custom
        module, <command>httpd</command> makes Subversion repositories
-      available to clients via the WebDAV/DeltaV protocol, which is an
-      extension to HTTP 1.1 (see <ulink url="http://www.webdav.org/"/>
-      for more information).  This protocol takes the ubiquitous HTTP
-      protocol that is the core of the World Wide Web, and adds
-      writing—specifically, versioned
+      available to clients via the WebDAV/DeltaV<footnote><para>See
+      <ulink url="http://www.webdav.org/"/>.</para></footnote>
+      protocol, which is an extension to HTTP 1.1.  This protocol
+      takes the ubiquitous HTTP protocol that is the core of the World
+      Wide Web, and adds writing—specifically, versioned
        writing—capabilities.  The result is a standardized,
        robust system that is conveniently packaged as part of the
        Apache 2.0 software, supported by numerous operating systems and
        third-party products, and doesn't require network administrators
        to open up yet another custom port.<footnote><para>They really
-      hate doing that.</para></footnote>  While an Apache-Subversion
+      hate doing that.</para></footnote> While an Apache-Subversion
        server has more features than <command>svnserve</command>, it's
        also a bit more difficult to set up.  With flexibility often
        comes more complexity.</para>
@@ -1910,12 +1911,13 @@
        <sect3 id="svn.serverconfig.httpd.authn.basic">
          <title>Basic authentication</title>

-        <para>The easiest way to authenticate a client is via the
-          HTTP Basic authentication mechanism, which simply uses a
-          username and password to verify a user's identity.  Apache
-          provides the <command>htpasswd</command> utility
-          (<ulink  
url="http://httpd.apache.org/docs/current/programs/htpasswd.html"/>)
-          for managing files containing usernames and passwords.</para>
+        <para>The easiest way to authenticate a client is via the HTTP
+          Basic authentication mechanism, which simply uses a username
+          and password to verify a user's identity.  Apache provides
+          the <command>htpasswd</command> utility<footnote><para>See
+          <ulink  
url="http://httpd.apache.org/docs/current/programs/htpasswd.html"
+          />.</para></footnote> for managing files containing
+          usernames and passwords.</para>

          <warning>
            <para>Basic authentication is <emphasis>extremely</emphasis>
@@ -2054,11 +2056,13 @@
          <para>Notice that <literal>AuthType</literal> is now set to
            <literal>Digest</literal>, and we specify a different path
            for <literal>AuthUserFile</literal>.  Digest authentication
-          uses a different file format than Basic authentication;
-          it is created using Apache's <command>htdigest</command>
-          utility (<ulink  
url="http://httpd.apache.org/docs/current/programs/htdigest.html"/>)
-          rather than <command>htpasswd</command>.
-          Digest authentication also has the additional concept of a
+          uses a different file format than Basic authentication; it
+          is created using Apache's <command>htdigest</command>
+          utility<footnote><para>See
+          <ulink  
url="http://httpd.apache.org/docs/current/programs/htdigest.html"
+          />.</para></footnote> rather
+          than <command>htpasswd</command>.  Digest authentication
+          also has the additional concept of a
            <quote>realm</quote>, which must match the value of the
            <literal>AuthName</literal> directive.  The password file
            can be created as follows:</para>
@@ -3510,17 +3514,7 @@
        world-readable to all users.  Once all users have read access to
        the repositories, you can give explicit
        <literal>rw</literal> permission to certain users on specific
-      subdirectories within specific repositories.</para>
-
-    <para>The asterisk variable (<literal>*</literal>) is also worth
-      special mention because it's the
-      <emphasis>only</emphasis> pattern that matches an anonymous
-      user.  If you've configured your server block to allow a mixture
-      of anonymous and authenticated access, all users start out
-      accessing anonymously.  The server looks for a
-      <literal>*</literal> value defined for the path being accessed;
-      if it can't find one, it demands real authentication from
-      the client.</para>
+      subdirectories within specific repositories.

      <para>The access file also allows you to define whole groups of
        users, much like the Unix <filename>/etc/group</filename>