[svnbook commit] r1750 - trunk/src/en/book
cmpilato
svnbook-dev at red-bean.com
Mon Oct 24 11:48:43 CDT 2005
Author: cmpilato
Date: Mon Oct 24 11:48:39 2005
New Revision: 1750
Modified:
trunk/src/en/book/appb.xml
Log:
Rework Appendix B to have the natural organizational heirarchy that its text
described, but that its layout failed to support.
Modified: trunk/src/en/book/appb.xml
==============================================================================
--- trunk/src/en/book/appb.xml (original)
+++ trunk/src/en/book/appb.xml Mon Oct 24 11:48:39 2005
@@ -153,7 +153,7 @@
<varlistentry>
<term>Per-resource versioning</term>
<listitem>
- <para> Like CVS and other version-control systems,
+ <para>Like CVS and other version-control systems,
DeltaV assumes that each resource has a potentially
infinite number of states. A client begins by placing
a resource under version control using the new
@@ -228,7 +228,7 @@
</variablelist>
- </sect2>
+ </sect2>
</sect1>
@@ -311,7 +311,7 @@
<!-- ================================================================= -->
<!-- ================================================================= -->
<sect1 id="svn.webdav.autoversioning">
- <title>Autoversioning </title>
+ <title>Autoversioning</title>
<para>While the Subversion client is not a full DeltaV client, nor
the Subversion server a full DeltaV server, there's still a
@@ -350,7 +350,7 @@
directive within the <filename>httpd.conf</filename> Location
block, like so:</para>
- <screen>
+ <screen>
<Location /repos>
DAV svn
SVNPath /path/to/repository
@@ -358,7 +358,6 @@
</Location>
</screen>
-
<para>When SVNAutoversioning is active, write requests from WebDAV
clients result in automatic commits. A generic log message is
auto-generated and attached to each revision.</para>
@@ -393,359 +392,66 @@
<sect1 id="svn.webdav.clients">
<title>Client Interoperability</title>
- <para>In this section, we'll describe the most common WebDAV clients (at
- the time of writing), and how well they operate against an
- autoversioning mod_dav_svn server.</para>
-
- <para>All WebDAV clients fall into one of three categories. These
- categories are the main definers of what users can and cannot
- do.</para>
-
- <variablelist>
-
- <varlistentry>
- <term>Standalone application</term>
-
- <listitem>
- <para>The WebDAV functionality is buried within a single
- application. For example, Microsoft Word is able to open a
- file directly from a URL. It locks the file when this
- happens, and every subsequent <quote>save</quote> command
- results in a PUT request.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>File-explorer extension</term>
-
- <listitem>
- <para>The WebDAV functionality is an extension to a GUI
- program that is normally used to browse filesystems,
- either local or remote. For example, Windows Explorer is
- able to browse a WebDAV server as a <quote>network
- place</quote>. Users can drag files to and from the
- desktop, or can rename, copy, or delete files in the usual
- way. But because it's only a feature of the
- file-explorer, the DAV share isn't visible to ordinary
- applications. All DAV interaction must happen through the
- explorer interface.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Filesystem implementation</term>
-
- <listitem>
- <para>This the best sort of WebDAV client. It's implemented
- as a low-level filesystem (typically within the operating
- system's kernel.) This means that the DAV share is
- mounted like any other network filesystem, similar to
- mounting an NFS share on Unix, or attaching an SMB share
- as drive-letter in Windows. As a result, this sort of
- client provides completely transparent read/write WebDAV
- access to all programs. Applications aren't even aware
- that WebDAV requests are happening.</para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- <para>There are many WebDAV clients, far too many to list. Here
- we provide some details about our experiences with some of the
- more popular ones.</para>
-
- <table id="svn.webdav.clients.tbl-1">
- <title>Common WebDAV Clients</title>
- <tgroup cols="4">
- <thead>
- <row>
- <entry>DAV Client</entry>
- <entry>Standalone</entry>
- <entry>File-explorer</entry>
- <entry>Filesystem</entry>
- </row>
- </thead>
- <tbody>
-
- <row>
- <entry>Windows Webfolders</entry>
- <entry></entry>
- <entry>x</entry>
- <entry>x</entry>
- </row>
-
- <row>
- <entry>WebDrive</entry>
- <entry></entry>
- <entry></entry>
- <entry>x</entry>
- </row>
-
- <row>
- <entry>NetDrive</entry>
- <entry></entry>
- <entry></entry>
- <entry>x</entry>
- </row>
-
- <row>
- <entry>Mac OS X</entry>
- <entry></entry>
- <entry></entry>
- <entry>x</entry>
- </row>
-
- <row>
- <entry>GNOME Nautilus</entry>
- <entry></entry>
- <entry>x</entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>KDE Konqueror</entry>
- <entry></entry>
- <entry>x</entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>Linux davfs2</entry>
- <entry></entry>
- <entry></entry>
- <entry>x</entry>
- </row>
-
- <row>
- <entry>Cadaver</entry>
- <entry>x</entry>
- <entry></entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>DAV Explorer</entry>
- <entry>x</entry>
- <entry></entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>Microsoft Office</entry>
- <entry>x</entry>
- <entry></entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>Dreamweaver</entry>
- <entry>x</entry>
- <entry></entry>
- <entry></entry>
- </row>
-
- <row>
- <entry>Photoshop</entry>
- <entry>x</entry>
- <entry></entry>
- <entry></entry>
- </row>
-
- </tbody>
- </tgroup>
- </table>
+ <para>All WebDAV clients fall into one of three
+ categories—standalone applications, file-explorer
+ extensions, or filesystem implementations. These categories
+ broadly define the types of WebDAV functionality available to
+ users. In this section, we'll describe these categories, the
+ most common WebDAV clients in them, and how well they operate
+ against an autoversioning mod_dav_svn server.</para>
<!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.windows">
- <title>Windows Webfolders, WebDrive, Netdrive</title>
-
- <para>Microsoft was one of the original backers of the WebDAV
- specification, and first started shipping a client in Windows
- 98, known as <quote>Webfolders</quote>. This client was also
- shipped in Windows NT4 and 2000.</para>
-
- <para>The original Webfolders client was an extension to
- Explorer, the main GUI program used to browse filesystems. It
- works well enough. In Windows 98, the feature might need to
- be explicitly installed if Webfolders aren't already visible
- inside <quote>My Computer</quote>. In Windows 2000, simply
- add a new <quote>network place</quote>, enter the URL, and the
- WebDAV share will pop up for browsing.</para>
-
- <para>With the release of Windows XP, Microsoft started shipping
- a new implementation of Webfolders, known as the <quote>WebDAV
- mini-redirector</quote>. The new implementation is a
- filesystem-level client, allowing WebDAV shares to be mounted
- as drive letters. Unfortunately, this implementation is
- incredibly buggy. The client usually tries to convert http
- URLs (<literal>http://host/repos</literal>) into UNC share
- notation (<literal>\\host\repos</literal>); it also often
- tries to use Windows Domain authentication to respond to
- basic-auth HTTP challenges, sending usernames as
- <literal>HOST\username</literal>. These interoperability
- problems are severe and documented in numerous places around
- the web, to the frustration of many users. Even Greg Stein,
- the original author of Apache's WebDAV module, recommends
- against trying to use XP Webfolders against an Apache
- server.</para>
-
- <para>It turns out that the original
- <quote>Explorer-only</quote> Webfolders implementation isn't
- dead in XP, it's just buried. It's still possible to find it
- by using this technique:</para>
-
- <orderedlist>
-
- <listitem>
- <para>Go to 'Network Places'.</para>
- </listitem>
-
- <listitem>
- <para>Add a new network place.</para>
- </listitem>
-
- <listitem>
- <para>When prompted, enter the URL of the repository, but
- <emphasis>include a port number</emphasis> in the URL.
- For example, <literal>http://host/repos</literal> would be
- entered as <literal>http://host:80/repos</literal> instead.
- </para>
- </listitem>
-
- <listitem>
- <para>Respond to any authentication prompts.</para>
- </listitem>
-
- </orderedlist>
-
- <para>There are a number of other rumored workarounds to the
- problems, but none of them seem to work on all versions and
- patchlevels of Windows XP. In our tests, only the previous
- algorithm seems to work consistently on every system. The
- general consensus of the WebDAV community is:</para>
-
- <itemizedlist>
- <listitem>
- <para>Avoid the new Webfolders implementation, use the old
- one.</para>
- </listitem>
-
- <listitem>
- <para>If you need real a real filesystem-level client for
- Windows XP, then use either WebDrive or NetDrive.</para>
- </listitem>
- </itemizedlist>
-
- <para>Both WebDrive and NetDrive are excellent commercial
- products which allows a WebDAV share to be attached as drive
- letters. We've had nothing but success with these products.
- At the time of writing, WebDrive can be purchased from South
- River Technologies (<ulink
- url="http://www.southrivertech.com"/>). NetDrive ships with
- Netware, is free of charge, and can be found by searching the
- web for <quote>netdrive.exe</quote>. (If that sounds odd to
- you, you're not alone. See this page on Novell's website:
- <ulink
- url="http://www.novell.com/coolsolutions/qna/999.html"/>)</para>
-
- </sect2>
-
+ <sect2 id="svn.webdav.clients.standalone-applications">
+ <title>Standalone WebDAV applications</title>
- <!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.macosx">
- <title>Mac OS X</title>
-
- <para>Apple's OS X operating system has an integrated
- filesystem-level WebDAV client. From the Finder, select the
- <guimenuitem>Connect to Server</guimenuitem> item from the
- <guimenu>Go menu</guimenu>. Enter a WebDAV URL, and it
- appears as a disk on the desktop, just like any other mounted
- volume.<footnote><para>From the Darwin terminal, one can also
- run <literal>mount -t webdav URL
- /mountpoint</literal></para></footnote>.</para>
-
- <para>Note that if your mod_dav_svn is older than version 1.2,
- OS X will refuse to mount the share as read-write; it will
- appear as read-only. This is because the OS X insists on
- locking support for read-write shares, and the ability to lock
- files first appeared in Subversion 1.2.</para>
-
- <para>One more word of warning: OS X's WebDAV client can
- sometimes be overly sensitive to HTTP redirects. If OS X is
- unable to mount the repository at all, you may need to enable
- the BrowserMatch directive in the Apache server's
- <filename>httpd.conf</filename>:</para>
-
- <screen>
-BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
-</screen>
-
- </sect2>
-
-
- <!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.linux-de">
- <title>Nautilus, Konqueror</title>
-
- <para>Nautilus is the official file manager/browser for the
- GNOME desktop (<ulink url="http://www.gnome.org"/>), and
- Konqueror is the manager/browser for KDE desktop (<ulink
- url="http://www.kde.org"/>). Both of these applications have
- an explorer-level WebDAV client built-in, and operate just
- fine against an autoversioning repository.</para>
-
- <para>In GNOME's Nautilus, from the <guimenu>File
- menu</guimenu>, select <guimenuitem>Open
- location</guimenuitem> and enter the URL. The repository
- should then be displayed like any other filesystem.</para>
-
- <para>In KDE's Konqueror, you need to use the
- <literal>webdav://</literal> scheme when entering the URL in
- the location bar. If you enter an <literal>http://</literal>
- URL, Konqueror will behave like an ordinary web browser.
- You'll likely see the generic HTML directory listing produced
- by mod_dav_svn. By entering
- <literal>webdav://host/repos</literal> instead of
- <literal>http://host/repos</literal>, Konqueror becomes a
- WebDAV client and displays the repository as a
- filesystem.</para>
-
- </sect2>
-
- <!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.linux-fs">
- <title>Linux davfs2</title>
+ <para>A WebDAV application is a program which contains built-in
+ functionality for speaking WebDAV protocols with a WebDAV
+ server. We'll cover some of the most popular programs with
+ this kind of WebDAV support.</para>
- <para>Linux davfs2 is a filesystem module for the Linux kernel,
- whose development is located at <ulink
- url="http://dav.sourceforge.net/"/>. Once installed, a WebDAV
- network share can be mounted with the usual Linux mount
- command:</para>
-
- <screen>
-mount.davfs http://host/repos /mnt/dav
-</screen>
-
- </sect2>
-
- <!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.free-apps">
- <title>Cadaver, DAV Explorer</title>
+ <sect3 id="svn.webdav.clients.win-apps">
+ <title>Microsoft Office, Dreamweaver, Photoshop</title>
+
+ <para>On Windows, there are several well-known applications
+ that contain integrated WebDAV client functionality, such as
+ Microsoft's Office,
+ <footnote>
+ <para>WebDAV support was removed from Microsoft Access for
+ some reason, but exists in the rest of the Office
+ suite.</para>
+ </footnote>
+ Adobe's Photoshop, and Macromedia's Dreamweaver programs.
+ They're able to directly open and save to URLs, and tend to
+ make heavy use of WebDAV locks when editing a file.</para>
+
+ <para>Note that while many of these programs also exist for
+ the Mac OS X, they do not appear to support WebDAV directly
+ on that platform. In fact, on Mac OS X, the
+ <guimenu>File->Open</guimenu> dialog box doesn't allow
+ one to type a path or URL at all. It's likely that the the
+ WebDAV features were deliberately left out of Macintosh
+ versions of these programs, since OS X already provides such
+ excellent low-level filesystem support for WebDAV.</para>
+
+ </sect3>
- <para>Cadaver is a bare-bones Unix commandline program for
- browsing and changing WebDAV shares. Like the Subversion
- client, it uses the neon HTTP library—not surprisingly,
- both neon and cadaver are written by the same author. Cadaver
- is free sofware (GPL license) and is available at <ulink
- url="http://www.webdav.org/cadaver/"/>.</para>
-
- <para>Using cadaver is similar to using a commandline FTP
- program, and thus it's extremely useful for basic WebDAV
- debugging. It can be used to upload or download files in a
- pinch, and also to examine properties, copy, move, lock or
- unlock files:</para>
-
- <screen>
+ <sect3 id="svn.webdav.clients.free-apps">
+ <title>Cadaver, DAV Explorer</title>
+
+ <para>Cadaver is a bare-bones Unix commandline program for
+ browsing and changing WebDAV shares. Like the Subversion
+ client, it uses the neon HTTP library—not surprisingly,
+ both neon and cadaver are written by the same author. Cadaver
+ is free sofware (GPL license) and is available at <ulink
+ url="http://www.webdav.org/cadaver/"/>.</para>
+
+ <para>Using cadaver is similar to using a commandline FTP
+ program, and thus it's extremely useful for basic WebDAV
+ debugging. It can be used to upload or download files in a
+ pinch, and also to examine properties, copy, move, lock or
+ unlock files:</para>
+
+ <screen>
$ cadaver http://host/repos
dav:/repos/> ls
Listing collection `/repos/': succeeded.
@@ -763,43 +469,221 @@
Progress: [=============================>] 100.0% of 1461 bytes succeeded.
</screen>
- <para>DAV Explorer is another standalone WebDAV client, written
- in Java. It's under a free Apache-like license and is
- available at <ulink url="http://www.ics.uci.edu/~webdav/"/>.
- DAV Explorer does everything cadaver does, but has the
- advantages of being portable and being more user-friendly GUI
- application. It's also one of the first clients to support
- the new WebDAV Access Control Protocol (RFC 3744).</para>
-
- <para>Of course, DAV Explorer's ACL support is useless in this
- case, since mod_dav_svn doesn't support it. The fact that
- both Cadaver and DAV Explorer support some limited DeltaV
- commands isn't particularly useful either, since they don't
- allow <literal>MKACTIVITY</literal> requests. But it's not
- relevant anyway; we're assuming all of these clients are
- operating against an autoversioning repository.</para>
-
+ <para>DAV Explorer is another standalone WebDAV client, written
+ in Java. It's under a free Apache-like license and is
+ available at <ulink url="http://www.ics.uci.edu/~webdav/"/>.
+ DAV Explorer does everything cadaver does, but has the
+ advantages of being portable and being more user-friendly GUI
+ application. It's also one of the first clients to support
+ the new WebDAV Access Control Protocol (RFC 3744).</para>
+
+ <para>Of course, DAV Explorer's ACL support is useless in this
+ case, since mod_dav_svn doesn't support it. The fact that
+ both Cadaver and DAV Explorer support some limited DeltaV
+ commands isn't particularly useful either, since they don't
+ allow <literal>MKACTIVITY</literal> requests. But it's not
+ relevant anyway; we're assuming all of these clients are
+ operating against an autoversioning repository.</para>
+
+ </sect3>
</sect2>
-
+
<!-- =============================================================== -->
- <sect2 id="svn.webdav.clients.win-apps">
- <title>Microsoft Office, Dreamweaver, Photoshop</title>
+ <sect2 id="svn.webdav.clients.file-explorer-extensions">
+ <title>File-explorer WebDAV extensions</title>
- <para>These are large well-known applications that contain
- integrated WebDAV client functionality. They're able to
- directly open a URL, save to a URL, and tend to make heavy use
- of WebDAV locks when editing a file.</para>
-
- <para>It appears that only the Windows versions of these
- programs support WebDAV. On Mac OS X, the
- <quote>File->Open</quote> dialog box doesn't allow one to type
- a path or URL at all. It's likely that the the WebDAV
- features were deliberately left out of Macintosh versions of
- these programs, since OS X already provides such excellent
- low-level filesystem support for WebDAV.</para>
+ <para>Some popular file explorer GUI programs support WebDAV
+ extensions which allow a user to browse a DAV share as if it
+ was just another directory on the local computer, and allowing
+ basic tree editing operations on the items in that share. For
+ example, Windows Explorer is able to browse a WebDAV server as
+ a <quote>network place</quote>. Users can drag files to and
+ from the desktop, or can rename, copy, or delete files in the
+ usual way. But because it's only a feature of the
+ file-explorer, the DAV share isn't visible to ordinary
+ applications. All DAV interaction must happen through the
+ explorer interface.</para>
+ <sect3 id="svn.webdav.clients.windows">
+ <title>Windows Webfolders</title>
+
+ <para>Microsoft was one of the original backers of the WebDAV
+ specification, and first started shipping a client in Windows
+ 98, known as <quote>Webfolders</quote>. This client was also
+ shipped in Windows NT4 and 2000.</para>
+
+ <para>The original Webfolders client was an extension to
+ Explorer, the main GUI program used to browse filesystems. It
+ works well enough. In Windows 98, the feature might need to
+ be explicitly installed if Webfolders aren't already visible
+ inside <quote>My Computer</quote>. In Windows 2000, simply
+ add a new <quote>network place</quote>, enter the URL, and the
+ WebDAV share will pop up for browsing.</para>
+
+ <para>With the release of Windows XP, Microsoft started shipping
+ a new implementation of Webfolders, known as the <quote>WebDAV
+ mini-redirector</quote>. The new implementation is a
+ filesystem-level client, allowing WebDAV shares to be mounted
+ as drive letters. Unfortunately, this implementation is
+ incredibly buggy. The client usually tries to convert http
+ URLs (<literal>http://host/repos</literal>) into UNC share
+ notation (<literal>\\host\repos</literal>); it also often
+ tries to use Windows Domain authentication to respond to
+ basic-auth HTTP challenges, sending usernames as
+ <literal>HOST\username</literal>. These interoperability
+ problems are severe and documented in numerous places around
+ the web, to the frustration of many users. Even Greg Stein,
+ the original author of Apache's WebDAV module, recommends
+ against trying to use XP Webfolders against an Apache
+ server.</para>
+
+ <para>It turns out that the original
+ <quote>Explorer-only</quote> Webfolders implementation isn't
+ dead in XP, it's just buried. It's still possible to find it
+ by using this technique:</para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>Go to 'Network Places'.</para>
+ </listitem>
+
+ <listitem>
+ <para>Add a new network place.</para>
+ </listitem>
+
+ <listitem>
+ <para>When prompted, enter the URL of the repository, but
+ <emphasis>include a port number</emphasis> in the URL.
+ For example, <literal>http://host/repos</literal> would be
+ entered as <literal>http://host:80/repos</literal> instead.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Respond to any authentication prompts.</para>
+ </listitem>
+
+ </orderedlist>
+
+ <para>There are a number of other rumored workarounds to the
+ problems, but none of them seem to work on all versions and
+ patchlevels of Windows XP. In our tests, only the previous
+ algorithm seems to work consistently on every system. The
+ general consensus of the WebDAV community is that you should
+ avoid the new Webfolders implementation and use the old one
+ instead, and that if you need real a real filesystem-level
+ client for Windows XP, then use a third-party program like
+ WebDrive or NetDrive.</para>
+
+ </sect3>
+
+ <sect3 id="svn.webdav.clients.linux-de">
+ <title>Nautilus, Konqueror</title>
+
+ <para>Nautilus is the official file manager/browser for the
+ GNOME desktop (<ulink url="http://www.gnome.org"/>), and
+ Konqueror is the manager/browser for KDE desktop (<ulink
+ url="http://www.kde.org"/>). Both of these applications have
+ an explorer-level WebDAV client built-in, and operate just
+ fine against an autoversioning repository.</para>
+
+ <para>In GNOME's Nautilus, from the <guimenu>File
+ menu</guimenu>, select <guimenuitem>Open
+ location</guimenuitem> and enter the URL. The repository
+ should then be displayed like any other filesystem.</para>
+
+ <para>In KDE's Konqueror, you need to use the
+ <literal>webdav://</literal> scheme when entering the URL in
+ the location bar. If you enter an <literal>http://</literal>
+ URL, Konqueror will behave like an ordinary web browser.
+ You'll likely see the generic HTML directory listing produced
+ by mod_dav_svn. By entering
+ <literal>webdav://host/repos</literal> instead of
+ <literal>http://host/repos</literal>, Konqueror becomes a
+ WebDAV client and displays the repository as a
+ filesystem.</para>
+
+ </sect3>
</sect2>
+ <sect2 id="svn.webdav.clients.filesystem-implementation">
+ <title>WebDAV filesystem implementation</title>
+
+ <para>The WebDAV filesystem implementation is arguably the best
+ sort of WebDAV client. It's implemented as a low-level
+ filesystem module, typically within the operating system's
+ kernel. This means that the DAV share is mounted like any
+ other network filesystem, similar to mounting an NFS share on
+ Unix, or attaching an SMB share as drive-letter in Windows.
+ As a result, this sort of client provides completely
+ transparent read/write WebDAV access to all programs.
+ Applications aren't even aware that WebDAV requests are
+ happening.</para>
+
+ <sect3 id="svn.webdav.clients.windows">
+ <title>WebDrive, NetDrive</title>
+
+ <para>Both WebDrive and NetDrive are excellent commercial
+ products which allows a WebDAV share to be attached as drive
+ letters in Windows. We've had nothing but success with
+ these products. At the time of writing, WebDrive can be
+ purchased from South River Technologies (<ulink
+ url="http://www.southrivertech.com"/>). NetDrive ships with
+ Netware, is free of charge, and can be found by searching
+ the web for <quote>netdrive.exe</quote>. Though it is
+ freely available online, users are required to have a
+ Netware license. (If any of that sounds odd to you, you're
+ not alone. See this page on Novell's website: <ulink
+ url="http://www.novell.com/coolsolutions/qna/999.html"/>)</para>
+
+ </sect3>
+
+ <sect3 id="svn.webdav.clients.macosx">
+ <title>Mac OS X</title>
+
+ <para>Apple's OS X operating system has an integrated
+ filesystem-level WebDAV client. From the Finder, select the
+ <guimenuitem>Connect to Server</guimenuitem> item from the
+ <guimenu>Go menu</guimenu>. Enter a WebDAV URL, and it
+ appears as a disk on the desktop, just like any other mounted
+ volume.<footnote><para>From the Darwin terminal, one can also
+ run <literal>mount -t webdav URL
+ /mountpoint</literal></para></footnote>.</para>
+
+ <para>Note that if your mod_dav_svn is older than version 1.2,
+ OS X will refuse to mount the share as read-write; it will
+ appear as read-only. This is because the OS X insists on
+ locking support for read-write shares, and the ability to lock
+ files first appeared in Subversion 1.2.</para>
+
+ <para>One more word of warning: OS X's WebDAV client can
+ sometimes be overly sensitive to HTTP redirects. If OS X is
+ unable to mount the repository at all, you may need to enable
+ the BrowserMatch directive in the Apache server's
+ <filename>httpd.conf</filename>:</para>
+
+ <screen>
+BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
+</screen>
+
+ </sect3>
+
+ <sect3 id="svn.webdav.clients.linux-fs">
+ <title>Linux davfs2</title>
+
+ <para>Linux davfs2 is a filesystem module for the Linux kernel,
+ whose development is located at <ulink
+ url="http://dav.sourceforge.net/"/>. Once installed, a WebDAV
+ network share can be mounted with the usual Linux mount
+ command:</para>
+
+ <screen>
+$ mount.davfs http://host/repos /mnt/dav
+</screen>
+
+ </sect3>
+ </sect2>
</sect1>
</appendix>
More information about the svnbook-dev
mailing list